4 ms·
The problem for web browsers is that markdown is technically a superset of HTML.
by inopinatus 9mo ago
The problem for web browsers is that markdown is technically a superset of HTML.
- bborud 9mo agoWhy is this a problem? To me it sounds like a it would be an advantage because you have everything you need to render it already built into the software.
- inopinatus 9mo agoRendering is trivial. The issue is standards, and the DOM. No-one can write a Markdown implementation for the core of any major web browser in a form that is simultaneously acceptable to both their technical and political governance. Best you’ll get is a plugin. Strictly arm’s reach. Translation only.
- bborud 9mo agoI'm not quite sure I understand what you are saying. Is the essence of what you are saying that it is hard to agree on a spec for the Markdown (and how it is translated to HTML or directly to DOM?) Or that this represents a technical challenge I don't understand?
- pwdisswordfishy 9mo agoWhy is it a problem for web browsers?
- dpe82 9mo agoIn what ways is it a superset? What can you express in markdown that can't be expressed in HTML?
- yencabulator 9mo agoI think you mean that any markdown byte sequence will also parse with some results using an HTML5 parser? Content-Type should fix that. Easy enough to associate *.md with one on most static servers too.