expanding or continuing from (with modular posts for ease of maintenance by admins (a.k.a. mods a.k.a. leaders)
lichess.org/forum/team-css-javascript-coding-on-lichess/opening-names-visible-at-all-times-in-analysis-boardThis may be a departure from original format, but now all threads are archived and I am too laze to create a new team with different content (i.e. Thread creation) policy or directive. modular again , as self-editorial, valid until reacted to or moot.
Recap: Concomitantly to the COVID pandemic awareness situation (and confinement) consequences resulting in a spike increase in lichess player base size, we have experienced diverse modifications to the front-end user experience as consequence to experiments on server load streamlining for the duration of the transition to bigger or better hardware infrastructure.
This topic was triggered by the recent UI changes, and my experimenting with collaboration on the feature of lichess Studies. This is an interesting research/teaching/writing tool that has far-reaching possibilities in modernizing the art or methods of chess learning, teaching, or researching, in that it allows for interaction, multi-directional inputs at various paces, promising to be inclusive of many types of chess player and lovers and their various learning ambitions, and cognitive/thinking/learning styles.
"Opening name placement demotion":
There are many thread in main forum about where have opening names gone,
--- it has disappeared from its usual top bar placement on the move list.
That is for all lichess pages based on the move list explorer of the baseline analysis page:
--- the core "module" without engine, or opening book/table/explorer, the minimal version.
It has been demoted to the use of optional "opening explorer" module. In its header. possibly the optional use of this makes it a reduced back-end frequency of requests for that information, for in-analysis, online subset of player base.
Team topic idea(s):
Depending on whether this is only temporary (which is fine with me),, or not, it would provide for new CSS selectors to study, with respect to this topic follow-up.
Study scripting, Chapter specificity, CSS selectors:
While inspecting with Devtools for Chrome a Study chapter page with opening explorer triggered, I realized that the previously used CSS selectors may not apply there, or alternatively, could be tailored to target specific chapters:
In studies, Chapters, can be linked specifically within their study, by appending an additional hash suffix.
One idea I saw somewhere was using the flex property? I have 0 experience with this and don't completely know how it works, but it looks like it takes ids from the HTML and changes the order they appear? I wonder if it would be possible to select the opening explorer and reorder it to the top of the notation sheet.
Study scripting, URL target specificity, including chapters:
( up-stream from selector chapter specificity concern)
URL targeting of previous scripts for post-game analysis or correspondence analysis pages don't seem to cover the study pages, in my experience. That is not related to the temporary demotion, just that I did not care to mention it before.
But the chapter specificity option for CSS selector is based on the Chapter URL target specificity.
Making it this URL target question less trivial.
Until now, as needed to ensure non-scrolling visibility of all information on rendered page, I have been using quick and dirty overrides, at each UI updates, using reloads when those crude mods were too ugly. Overrides don't have to be crude, but since I would have to manually re-write them at each updates, I use Devtools commenting of styles corresponding to the CSS selector of interest, i.e. un-checking the style item box once selector chosen in DOM tree (for those new to Devtools).
So that's an added script tuning concern, although not lichess spike related, just my study feature new awareness.
With the above posts, that's two entry points for specificity regarding chapters.
#7 For example of my overrides quick and dirty commenting out of CSS selector specific styles, I have been using the flex style, but it is not sufficient: overflow and maxheight also come into play.
All three need to be commented out, with less Q&D work we could find the proper style perhaps that would make the triplet mod more careful. as that quick and dirty has ugly side-effect of other modules (all is rendered but some objects are way down the page, uselessly. It all depends on which sub-containers are attached to which parent, and the relativeness of their position with respect to their filiation tree.
adding to previous post:
Actually, I may have been wrong about the source of side-effects, for the Q&D approach, or partially incorrect.
The clearest source of side-effect, is the lumping in CSS code of many selectors into one styling statement (by grouping selectors), as I will show in other posts or threads (up to admin as to which is best). All objects on page specified by such grouping in CSS code, will affected by overriding commenting out (checkbox toggle out).
The other source, would be clearer in scripting experiments with various property values (I guess I don't know how to read the cascade from a given CSS source file, and perhaps will figure it out that way).
