[Feature] UserSetting to choose witch text editor is defualt (SimpleMDE, textarea, automatic) #4772

Closed
opened 2025-11-02 06:02:27 -06:00 by GiteaMirror · 11 comments
Owner

Originally created by @6543 on GitHub (Feb 2, 2020).

enhancement of #10099
as per lunny:

  • automatically, pc SimpleMDE and mobile textarea and this is the default.
  • always SimpleMDE
  • always textarea
Originally created by @6543 on GitHub (Feb 2, 2020). enhancement of #10099 as per lunny: * automatically, pc SimpleMDE and mobile textarea and this is the default. * always SimpleMDE * always textarea
GiteaMirror added the outdated/theme/markdowntype/proposal labels 2025-11-02 06:02:27 -06:00
Author
Owner

@lafriks commented on GitHub (Feb 2, 2020):

I would prefer it not to be user setting but being detected by device - mobile or not

@lafriks commented on GitHub (Feb 2, 2020): I would prefer it not to be user setting but being detected by device - mobile or not
Author
Owner

@guillep2k commented on GitHub (Feb 3, 2020):

Why not both? Personally I'd rather not use SimpleMDE if that leaves me out of the stock spell checker, mobile or not, but I can understand why most people will benefit from it.

@guillep2k commented on GitHub (Feb 3, 2020): Why not both? Personally I'd rather not use SimpleMDE if that leaves me out of the stock spell checker, mobile or not, but I can understand why most people will benefit from it.
Author
Owner

@lunny commented on GitHub (Feb 3, 2020):

We could have three options on user settings:

  • automatically, pc SimpleMDE and mobile textarea and this is the default.
  • always SimpleMDE
  • always textarea
@lunny commented on GitHub (Feb 3, 2020): We could have three options on user settings: - [ ] automatically, pc SimpleMDE and mobile textarea and this is the default. - [ ] always SimpleMDE - [ ] always textarea
Author
Owner

@6543 commented on GitHub (Feb 3, 2020):

@lunny nice proposal! because each like it different (example i would choose 3, but most will use 1? ...)

@6543 commented on GitHub (Feb 3, 2020): @lunny nice proposal! because each like it different (example i would choose 3, but most will use 1? ...)
Author
Owner

@corneliusroemer commented on GitHub (Dec 15, 2020):

What's the reason for textarea not being the default on mobile? Isn't SimpleMDE on mobile totally broken? Or does it work for most people just not me and a few unlucky other folks?

@corneliusroemer commented on GitHub (Dec 15, 2020): What's the reason for textarea not being the default on mobile? Isn't SimpleMDE on mobile totally broken? Or does it work for most people just not me and a few unlucky other folks?
Author
Owner

@zeripath commented on GitHub (Dec 15, 2020):

No one has coded or submitted a PR to do this.

@zeripath commented on GitHub (Dec 15, 2020): No one has coded or submitted a PR to do this.
Author
Owner

@corneliusroemer commented on GitHub (Dec 16, 2020):

#14017 isn't exactly a allowing the "user" to choose default editor, but it at least disables the broken WYSIWYG on mobile.

@corneliusroemer commented on GitHub (Dec 16, 2020): #14017 isn't exactly a allowing the "user" to choose default editor, but it at least disables the broken WYSIWYG on mobile.
Author
Owner

@6543 commented on GitHub (Dec 16, 2020):

didnt we migrated already on master to EasyMDE?

@6543 commented on GitHub (Dec 16, 2020): didnt we migrated already on master to EasyMDE?
Author
Owner

@corneliusroemer commented on GitHub (Dec 16, 2020):

@6543 You're right, PR #14017 isn't relevant really to this issue.

@corneliusroemer commented on GitHub (Dec 16, 2020): @6543 You're right, PR #14017 isn't relevant really to this issue.
Author
Owner

@henningoschwald commented on GitHub (Feb 13, 2021):

I understand there is currently no way to disable SimpleMDE either per user or globally, is this correct?

I am blind and therefore using a screen reader to interact with Gitea, unfortunately SimpleMDE is not accessible. When moving up or down with the error keys, usually screenreaders read the currently selected line, however in SimpleMDE I am not able to read the text. Furthermore, the keyboard focus is trapped within the text field. Usually the Tab key can be used to move the focus out of the editor, although SimpleMDE seems to block this, maybe to make the Tab key usable for indentation. This however breaks keyboard accessibility.

If you plan to get rid of the WYSIWYG editor anyway, I understand you don't want to put much efford into this, but at least a keyboard shortcut to switch to the plain text area would be great in the meantime. I'l see if I can come up with a PR for this.

Please let me know if there is already a way to disable SimpleMDE per user or for the whole instance. I don't need an editor tool bar with buttons to insert common formatting mark-up, a simple text area where I can enter markdown would be perfectly fine.

@henningoschwald commented on GitHub (Feb 13, 2021): I understand there is currently no way to disable SimpleMDE either per user or globally, is this correct? I am blind and therefore using a screen reader to interact with Gitea, unfortunately SimpleMDE is not accessible. When moving up or down with the error keys, usually screenreaders read the currently selected line, however in SimpleMDE I am not able to read the text. Furthermore, the keyboard focus is trapped within the text field. Usually the Tab key can be used to move the focus out of the editor, although SimpleMDE seems to block this, maybe to make the Tab key usable for indentation. This however breaks keyboard accessibility. If you plan to get rid of the WYSIWYG editor anyway, I understand you don't want to put much efford into this, but at least a keyboard shortcut to switch to the plain text area would be great in the meantime. I'l see if I can come up with a PR for this. Please let me know if there is already a way to disable SimpleMDE per user or for the whole instance. I don't need an editor tool bar with buttons to insert common formatting mark-up, a simple text area where I can enter markdown would be perfectly fine.
Author
Owner

@delvh commented on GitHub (Apr 3, 2023):

Isn't that pseudo-implemented with #23876 already?
It contains a switch to legacy button, which I think is the best way to handle it for anyone who wants the old easyMDE behavior (if anyone even wants that)

@delvh commented on GitHub (Apr 3, 2023): Isn't that pseudo-implemented with #23876 already? It contains a `switch to legacy button`, which I think is the best way to handle it for anyone who wants the old easyMDE behavior (if anyone even wants that)
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/gitea#4772