Comment by asdfalsrgkj
21 hours ago
How about:
- no scripts of any kind
- no cookies
- no forms
- all resources (e.g., styles, images) needed for display inlined
- a spacious minimum cap on data URI length
- elaborate the <a> tag a bit to allow a series of content addresses (hashes, IPFS, magnet URIs, etc.) for references
Basically, a "dead" subset of HTML suitable for distributing documents.
I keep writing the same comment every time this is brought up, but browsers need to support text/markdown.
Technically depending on the implementation, markdown is a superset of HTML.
You'll need to be more specific since there are many variants of Markdown and the original explicitly permits arbitrary html.
CommonMark is pretty standard (even if not perfect) and you're in the browser anyway so arbitrary html is not really a problem..
1 reply →
Markdown? Terrible "spec".
Browsers already support XML.
You can spin up a HTML-but-restricted XML grammar (with extra stuff even, like footnotes and stuff) and a CSS file in maybe half an hour, and it'll render in your browser just fine.
(Yeah, it'll be missing all the accessibility provisions, but you know, the base to build on is there, whereas "MarkDown in the browser" rendering has been often suggested and never implemented).