Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Community Feedback] Using a What-you-see-is-what-you-get markdown editor or not #30474

Open
delvh opened this issue Apr 14, 2024 · 8 comments
Open
Labels
issue/needs-feedback For bugs, we need more details. For features, the feature must be described in more detail

Comments

@delvh
Copy link
Member

delvh commented Apr 14, 2024

Hello everyone,

Historically, Gitea always had a Markdown editor that immediately previewed how the result would look like:
image

However, all existing editors we have experimented with turned out to have various unfixable bugs and were fundamentally flawed, worst of all regarding accessibility and that the end result can differ from what the editor displays.

As such, we have already deprecated our existing editor (EasyMDE) in 1.20.0.
Instead, you only see the text you entered:
image

Now, we are considering whether to drop the editor highlighting completely.

Warning

If you rely on the immediate preview how your comment will look like, please let your voice be heard in this issue.
If there is no huge demand, we will drop immediate Markdown highlighting in 1.23.0.

Important

You can still see how a text will be rendered by clicking on the Preview tab in every editor:
image

Important

Anything that is already present on the server (markdown files, issue comments, PR descriptions, PR reviews, …) is unaffected and will still render as Markdown.
Only the preview how your comments etc. will look like will be less immediate as you must first navigate to Preview.

@delvh delvh added the issue/needs-feedback For bugs, we need more details. For features, the feature must be described in more detail label Apr 14, 2024
@stuzer05
Copy link

What are current problems with preview tab? We use it. At least, if not features are supported, they can be disabled for preview. But it's essential for formatting an issue

@eeyrjmr
Copy link
Contributor

eeyrjmr commented Apr 14, 2024

What are current problems with preview tab? We use it. At least, if not features are supported, they can be disabled for preview.

No issue with preview tab
Issue with the editor (Write) tab "trying" to do some form of previewing.

@delvh delvh pinned this issue Apr 14, 2024
@KazzmanK
Copy link
Contributor

Never noticed that editor tab was trying to beautify text in any form. Crafting tables is a bit annoying, but my colleagues never complained about lack of wysiwyg

@Crown0815
Copy link

From my perspective, a WYSIWYG editor is nice to have, but not essential in any way due to the preview.
Github also has none.

@Pontiac76
Copy link

If yanking the ability to see in real time what the font-face of the text is going to be affects the security of the system, it shouldn't exist.

I love my WYSIWYG, and if it's removed, I'd be absolutely happy to write my own external WYSIWYG2MU (* to markup) for different markup sites. Gives me something to do.

@Pontiac76
Copy link

That said... would be kind of nice to have a real time optional side view of the content instead of having to switch tabs... even in a popup window or something for those lucky enough to have the screen real estate (I have 5 monitors, and sometimes I STILL run out of real estate!)

@wxiaoguang
Copy link
Contributor

I have a feeling that there are enough end users who still like the visual feedback by a "smart" markdown editor. Maybe some modern editors could replace the unmaintained EasyMDE.

For example, some editors:

@xxfogs
Copy link

xxfogs commented May 12, 2024

There are some non-technical people using my Gitea deployment and a WYSIWYG is particularly helpful for them as they're not too good at remembering markdown.

Preview works flawlessly but they still prefer seeing formatting immediately.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
issue/needs-feedback For bugs, we need more details. For features, the feature must be described in more detail
Projects
None yet
Development

No branches or pull requests

8 participants