You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The Xarray HTML repr assumes that light vs dark theming is stored in the html element's theme attribute (i.e., <html theme="dark"> or <html theme="light">).
However, the Sphinx Furo theme assumes that light vs dark theming is stored in the body element's data-theme attribute. As a result, if you use the Sphinx Furo theme for documentation and use Xarray HTML reprs, the Xarray HTML reprs do not display properly.
In truth, it seems that this comes down to the light vs dark theming not being standardized, which presents a problem of how to support multiple (possibly innumerable) different ways of specifying light or dark themes. That said, the Sphinx Furo theme has growing popularity, and I wonder if it could be supported as a special case (as is vscode dark themes).
What is your issue?
The Xarray HTML repr assumes that light vs dark theming is stored in the
html
element'stheme
attribute (i.e.,<html theme="dark">
or<html theme="light">
).However, the Sphinx Furo theme assumes that light vs dark theming is stored in the
body
element'sdata-theme
attribute. As a result, if you use the Sphinx Furo theme for documentation and use Xarray HTML reprs, the Xarray HTML reprs do not display properly.In truth, it seems that this comes down to the light vs dark theming not being standardized, which presents a problem of how to support multiple (possibly innumerable) different ways of specifying light or dark themes. That said, the Sphinx Furo theme has growing popularity, and I wonder if it could be supported as a special case (as is vscode dark themes).
To do this, one would need only modify one line of xarray/static/css/style.css:
xarray/xarray/static/css/style.css
Lines 16 to 17 in 0db3440
to:
If this is something that the Xarray community would support, I'm happy to put together a PR to do this.
The text was updated successfully, but these errors were encountered: