3 ms·
Take for example this page: https://getdoks.org/docs/start-here/getting-started/ https://getdoks.org/docs/start-here/getting-started/ ; I presume they're using
by deathanatos 3y ago
Take for example this page: https://getdoks.org/docs/start-here/getting-started/ https://getdoks.org/docs/start-here/getting-started/ ; I presume they're using their own tool to render their own documentation?
It seems to have some pretty basic bugs? Teletype renders as censoring, essentially: https://i.imgur.com/fyi32mR.png https://i.imgur.com/fyi32mR.png (what I can only presume is a light mode/dark mode half & half type situation…)
That doesn't convince me it's ready for prime time, though.
- cstrahan 3y agoYou may want to replace your browser with one that works: https://imgur.com/a/0IOKXY8 https://imgur.com/a/0IOKXY8 Screenshot taken on Firefox 123.0, on macOS 14.1.
- deathanatos 3y agoCuriously, that was FF 123.0b2, on macOS 13.1. Pretty close. These things are almost always bugs in JavaScript running on the site, IME. If I inspect a tt, it's setting a background of slate (black), and a foreground of "inherit", which is black. This is just messed up CSS, and the inspector seems to indicate that the JS on the page is crashing, and I see there's a sun/moon hieroglyph in the corner, i.e., there's JS for controlling light/dark mode. It seems like the code responsible for the light/dark mode must run one of these two things: document.documentElement.setAttribute('data-bs-theme', 'dark') document.documentElement.setAttribute('data-bs-theme', 'light') If neither happens, the page is left with the default styling, which is a bizarre mix of light/dark mode and contains the issues I've screenshotted. Neither happens, because slightly prior to that, the JS makes a call to a fallible function, and then subsequently fails to handle the error case. The uncaught exception kills it before it can call one of the two above lines, so we're left with a page with broken styling. It's a JavaScript bug.