4 ms·
That sounds like a good idea, until you remember that there is no officially agreed upon markdown spec. For content authors it'd be both fantastic if browsers c
by TheRealPomax 2y ago
That sounds like a good idea, until you remember that there is no officially agreed upon markdown spec. For content authors it'd be both fantastic if browsers could just go "you guys go fight it out, we're just gonna go with GitHub flavored markdown" but at the same time for browser makers that's taking a position on something that they have no stake in.
So writing or using someone else's custom element is pretty much your only option here.
- aylmao 2y agoyeah, I wasn't hypothesizing this as something that should be added natively to browsers. Web is complicated enough officially supporting 3 languages (or 6, if you consider wasm, webgl and wgsl) Though for what its worth, "no official agreed upon spec" didn't stop browsers before haha
- bityard 2y agoThere is a Markdown spec: https://commonmark.org https://commonmark.org Although of course in practice, commonmark renderers are not plentiful or up to date. In my experience, most library authors end up just implementing the bits of Markdown they care about and the behavior they prefer for the ambiguous parts.
- TheRealPomax 2y agoThere are multiple markdown specs. This is one of them, probably the most well-known, but certainly not the only one.
- alsetmusic 2y ago“This is my Markdown. There are many like it but this one is mine.”
- wrboyce 2y agoObligatory https://xkcd.com/927/ https://xkcd.com/927/
- MrVandemar 2y agohttps://hn.algolia.com/?dateRange=pastMonth&page=0&prefix=false&query=xkcd.com%2F927%2F&sort=byDate&type=comment https://hn.algolia.com/?dateRange=pastMonth&page=0&prefix=fa...