If you build websites, you inevitably run into problems. Maybe there’s no way to achieve an aspect of your design using CSS. Or maybe there’s a device feature you really wish you could tap into using JavaScript. Or perhaps the in-browser DevTools don’t give you a key insight you need to do your job. We want to hear about it!
Having to ship a script (and related resources like icons) that implements a WYSIWYG editor would be unnecessary in many cases if browsers provided native rendering of Markdown code and GUI elements to help enter it. Soft keyboards could be optimized to provide direct access to the formatting characters. The text transmitted to the server would be in Markdown according to RFC 7763/4.
This may also be applicable to <input type=text> with a limited set of possibilities.
title: native Markdown support in textarea date: 2023-05-04T21:25:09.373Z submitter: Christoph Päper number: 645422b5b943d000583d0ac6 tags: [ ] discussion: https://github.com/WebWeWant/webwewant.fyi/discussions/ status: [ discussing || in-progress || complete ] related:
title: url: type: [ article || explainer || draft || spec || note || discussion ]
Having to ship a script (and related resources like icons) that implements a WYSIWYG editor would be unnecessary in many cases if browsers provided native rendering of Markdown code and GUI elements to help enter it. Soft keyboards could be optimized to provide direct access to the formatting characters. The text transmitted to the server would be in Markdown according to RFC 7763/4.
This may also be applicable to
<input type=text>with a limited set of possibilities.If posted, this will appear at https://webwewant.fyi/wants/645422b5b943d000583d0ac6/