3 ms·
Why couldn't this be implemented as an extension in an existing browser? Sending and detecting a different content type (e.g. text/kyu) that triggers (for now)
by simonhamp 5y ago
Why couldn't this be implemented as an extension in an existing browser?
Sending and detecting a different content type (e.g. text/kyu) that triggers (for now) a JS parser that renders the markup used into the HTML that the browser understands
This feels like the best way to get some adoption without having to build a whole new browser
Edit: it also means you could flex away from Markdown and develop your own markup language and parser as and when the need arises
- Cyberdog 5y agoI haven't done any browser extension development. Is it possible for browser extensions to be able to read HTTP headers? Is that consistent across all browsers?
- simonhamp 5y agoYes and yes. The Web Extensions standard is coming along quite nicely (at least from my perspective) But even just targeting a single browser engine to start with feels appropriate just to get the concept out there and see how it flies
- ejones 5y agoIn fact it looks like there are already browser extensions that do this for Markdown: https://chrome.google.com/webstore/detail/markdown-viewer/ckkdlimhmcjmikdlpkmbgfkaikojcbjk?hl=en https://chrome.google.com/webstore/detail/markdown-viewer/ck... https://chrome.google.com/webstore/detail/markdown-preview-plus/febilkbfcbhebfnokafefeacimjdckgl?hl=en https://chrome.google.com/webstore/detail/markdown-preview-p...