Re:JavaScript growth and third parties
by azangru on Saturday December 15, 2018 @10:55AM
(#18688827)
Yep, my guess would be that they are using a markdown parser that generates a complete html document out of submitted markdown, and then they just stitch those parsed htmls together, like here (the processed_html method on the article instance):
Miraculously so! Anything I would have attempted to design would have crapped its pants at the look of this markup, but browsers heroically manage to display it as if nothing weird is happening. I take my hat off to their resilience.
Re:JavaScript growth and third parties
by bhalp1 on Saturday December 15, 2018 @11:00AM
(#18688867)
Yes. And actually, this is a mistake in our processing configuration. We don’t want separate body tags, but it hasn’t been a problem so we haven’t gotten around to fixing it.
https://github.com/thepracticaldev/dev.to/blob/master/app/vi...
> Browsers are very resistent to garbage markup
Miraculously so! Anything I would have attempted to design would have crapped its pants at the look of this markup, but browsers heroically manage to display it as if nothing weird is happening. I take my hat off to their resilience.