Fallback to simple editor (<textarea>?) would be useful for mobile

monaco-editor is hard to use on a mobile interface. It kind of works, but it's pretty painful to use.

I'd like to request a feature (possibly controlled by user, app using monaco-editor, or automatically based on a media query or similar) to fallback to a very simple editor, such as a <textarea> or perhaps an editable element, while keeping the same API of monaco-editor (IEditor).

Personally, I really like to use websites that use monaco-editor and I often use them on mobile. I don't really mind typing long text on mobile from time to time... But monaco-editor is often fighting me on it... I'd really appreciate having a way to fallback to a "dumber" editor (since I can leave without syntax highlighting, autocompletion, etc. for most use cases where I care about using mobile.)

I guess this could live in another layer or downstream consumer of monaco-editor (such as react-monaco-editor or perhaps an app would be able to implement two separate interfaces, one with a dumb editor), but I see an advantage of implementing this in monaco-editor itself so that it would easily track the API (IEditor), possibly implement easy controls that would automatically apply to all downstream consumers, avoid duplication, etc.

(NOTE: I'm not really knowledgeable in most of the technologies involved here, such as ES, React, etc. I'm filing this from an user's point of view. So forgive if I got some of the details incorrectly.)

Start by reviewing the IEditor API and the issue's proposed textarea or editable-element fallback. Determine whether the behavior belongs in monaco-editor or a downstream consumer such as react-monaco-editor, and define how a mobile fallback would preserve the existing API while omitting advanced editor features.