Parsoid output url for "enwiki > Wikipedia:Graphs_and_charts":
https://en.wikipedia.org/api/rest_v1/page/html/Wikipedia:Graphs_and_charts

https://ca.wikipedia.org/api/rest_v1/page/html/Ajuda:Gràfics_o_diagrames_estad%C3%ADstics

It looks like Parsoid output provides template information for most of parent divs via

{"template":{"target":{"wt":"bar box\n","href":"./Template:Bar_box"}

However, that info is localized - on ca.wikipedia.org the same line looks like

{"template":{"target":{"wt":"Gràfic de barres\n","href":"./Plantilla:Gràfic_de_barres"}

A unique template identifier available in Parsoid output would be more useful.

A unique template identifier available in Parsoid output would be more useful.

Isn't that what ./Template:Bar_box and ./Plantilla:Gràfic_de_barres are?

Theoretically the endpoint to could keep a list of any templates which need to be annotated in any way we would find useful - for example it could add a 'no-theme' class to all of the color bar divs of Bar_box output...

Lets discuss in planning or tech sync.

The existing 'baseline' CSS approach had the following goals:

• Don't blast dark mode users with bright light
• Use designer's colors palette for dark and sepia
• Address long-standing un-themed areas on orig Android implementation including on non EN-wikis which had been historically problematic (ties into the 'inline styles' challenge mentioned below)

Challenges:

• Handle MCS and MobileView consistently
• Work on older Android versions
• Work-arounds for widespread inline styles
• Performance

Some trade-offs were made at the time after discussion with @carolyn as relates to some less common elements' theming in order to achieve better theming on extremely common elements.

Some examples of the sorts of issues addressed by the 'baseline' css theming approach:

(these cropped up with a PR which unintentionally perturbed the 'baseline' approach, but was convenient for making some screenshots since these were almost the exact issues the baseline approach was tuned to address)

Issue	Fixed with 'baseline' css approach

Here are a few more issues but for these I was too lazy to go and get the fixed 'baseline' screenshots:

This has too much useful info to close for now, putting back in backlog.