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/
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:
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/