Apologies for abandoning this thread for awhile. I’m super excited to see how much discussion this has generated!
I spent some time checking out all the work you’ve done, and I’m super impressed! These are exactly the steps I would have wanted to start with before doing a polyfill. I can see this test suite being super useful, and the fact that you have a spec doc setup for PRs already is also amazing. As @jonathank suggested, it would be great if we could push in some tests for JS parsers.
I had totally forgotten that the W3C group existed, and that I was a member of it. Is everybody here that’s interested in pursuing this already a member of that group? Should we move the discussion there?
Custom elements (i.e. web components) did come up earlier in this thread. As I mentioned earlier, I personally believe that focusing on attributes rather than elements is the best way forward, but I certainly wouldn’t discount web components—such as the one @briankardell linked to—as an option.
Yup. IMO, that’s another reason why an attribute-based version, which could support different flavours (e.g.
format="markdown" flavor="gfm"), might be preferable. For me a goal would be not just to standardize a particular flavour of Markdown, but to standardize how those are and can be extended.
+1 for more generic, hence my suggestion of a
How has it been a bad idea?