4 ms·
> This didn't render in chrome, I had to look at the source of the page to read it. This is a classical example of doing css+js wrong. Loading the page with j
by kephra 13y ago
> This didn't render in chrome, I had to look at the source of the page to read it.
This is a classical example of doing css+js wrong.
Loading the page with js disabled, shows a blank page.
Disabling css, shows the content in a nearly non readable way, with extremely long lines.
Looking at the source tells me, that its not even HTML.
- krapp 13y agoIt's not even as if the content is being added by javascript, it's just markdown which gets parsed by js... the content is there, it's just being hidden by an inline css rule. That's the most annoying thing to me, although it's probably to prevent a FOUC. It is html though, but not really proper html. They're sending the html5 doctype for instance, but not declaring a content type, and I think (but i'm not certain) that the xmp tag is all but deprecated by now.