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
{{ message }}
This repository has been archived by the owner on Jan 30, 2024. It is now read-only.
It's actually quite a convoluted bug and a couple of things made it hard to discover:
The current CI takes the most recent package version available. In this case, that was the updated {DiagrammeR} which shipped with the faulty mermaid.css which had an overly aggressive css selector which set the opacity to 0.2, thereby rendering everything super hard to read. This problem should have been avoided (by @maxheld83) in the first place by freezing dependencies, and avoiding silent updates as per freeze deps #200 (just takes time).
This, in turn, lead to every webpage which included a DiagrammeR plot to include the faulty CSS. Webpages (such as /linux) without DiagrammeR were unaffected, making this hard to debug.
Making this harder to debug still, my local machine had apparently cached an older version of the CSS, which rendered the website perfectly on my local machine. (This is a common feature of browser to save on bandwidth -- you can avoid it by going into incognito mode).
This lead me to the faulty conclusion that this was browser issue, though it was actually just faulty css.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
The background color and font color combination makes it unreadable (at least in chrome)
.
The text was updated successfully, but these errors were encountered: