#90 Improve editor experience for issues

Closed
opened 4 months ago by Booteille · 11 comments

Actually, there is no interface for Markdown and no WYSIWYG editor for issues.

I would love to have something similar to the Wiki editor for users not used to Markdown.

Actually, there is no interface for Markdown and no WYSIWYG editor for issues. I would love to have something similar to the Wiki editor for users not used to Markdown.
hw commented 4 months ago
Owner

This would be a great improvement indeed. There are a couple of open gitea issues discussing this feature, see: https://github.com/go-gitea/gitea/issues/6975 and https://github.com/go-gitea/gitea/issues/5436.

This would be a great improvement indeed. There are a couple of open gitea issues discussing this feature, see: https://github.com/go-gitea/gitea/issues/6975 and https://github.com/go-gitea/gitea/issues/5436.
hw added the
gitea-related issue
label 4 months ago
6543 commented 1 month ago

gitea v1.11.0 will close this

gitea v1.11.0 will close this
hw commented 1 month ago
Owner

cool!

cool!
n0mad commented 1 month ago

Is there any way to get a more complete markdown editor to parse and edit the “readme” files? I'm trying to write some complex “landing” readme file using html flags with styles. In github works but not in here. (I assume that it's something related to gitea. If this is the wrong place to ask I'll open a separated issue)

Is there any way to get a more complete markdown editor to parse and edit the "readme" files? I'm trying to write some complex "landing" readme file using html flags with styles. In github works but not in here. (I assume that it's something related to gitea. If this is the wrong place to ask I'll open a separated issue)
ashimokawa commented 1 month ago
Owner

@n0mad

Do you have an example of what does not work?

Generally it is okay to report any issue that bugs you, whether it is giteas “fault” or not. Additionally reporting in to gitea is even better.

@n0mad Do you have an example of what does not work? Generally it is okay to report any issue that bugs you, whether it is giteas "fault" or not. Additionally reporting in to gitea is even better.
hw commented 1 month ago
Owner

Is there any way to get a more complete markdown editor to parse and edit the “readme” files? I’m trying to write some complex “landing” readme file using html flags with styles.

The gitea markdown sanitizer will remove all HTML that is considered potentially harmful, well possible that there are some false-positives or that it is overly restrictive.

Simple <img> markup works, as exemplified here: https://codeberg.org/hw/test/src/branch/master/README.md

If your particular case is not working but provably harmless, please report the issue!

> Is there any way to get a more complete markdown editor to parse and edit the “readme” files? I’m trying to write some complex “landing” readme file using html flags with styles. The gitea markdown sanitizer will remove all HTML that is considered potentially harmful, well possible that there are some false-positives or that it is overly restrictive. Simple `<img>` markup works, as exemplified here: https://codeberg.org/hw/test/src/branch/master/README.md If your particular case is not working but provably harmless, please report the issue!
n0mad commented 1 month ago

@ashimokawa

Sorry for the late reply, I've been busy.

The gitea markdown sanitizer will remove all HTML that is considered potentially harmful, well possible that there are some false-positives or that it is overly restrictive.

Is there a place to look what is potentially harmful for gitea?

As compared with github, this example works out of the box there, but not in here:

<h2 align="center">Lorem Ipsum Title is centered.</h2>

The text should be centered, but it isn't. Also (still making experiments in both github and codeberg to discover things) adding a margin style doesn't work.

style="margin-top: 15px;"

Here's a repo with the test file I'm testing: https://codeberg.org/n0mad/markdown-gitea-tests

@ashimokawa Sorry for the late reply, I've been busy. >The gitea markdown sanitizer will remove all HTML that is considered potentially harmful, well possible that there are some false-positives or that it is overly restrictive. Is there a place to look what is potentially harmful for gitea? As compared with github, this example works out of the box there, but not in here: `<h2 align="center">Lorem Ipsum Title is centered.</h2>` The text should be centered, but it isn't. Also (still making experiments in both github and codeberg to discover things) adding a margin style doesn't work. `style="margin-top: 15px;"` Here's a repo with the test file I'm testing: https://codeberg.org/n0mad/markdown-gitea-tests
hw commented 4 weeks ago
Owner

As wikipedia writes:

Since the initial description of Markdown contained ambiguities and unanswered questions, the implementations that appeared over the years have subtle differences and many come with syntax extensions.

Unfortunately “portable markdown” is a not a thing (yet), unless we restrict ourselves to the core feature set. Embedded HTML is not markdown (by definition), and as such almost never portable.

In your case two options might be worth considering:

  • contribute a patch for gitea's markdown renderer to support the markdown flavor you have in mind, or,
  • Generate proper HTML where you can use all formatting and publish it via https://pages.codeberg.org
As wikipedia writes: > Since the initial description of Markdown contained ambiguities and unanswered questions, the implementations that appeared over the years have subtle differences and many come with syntax extensions. Unfortunately "portable markdown" is a not a thing (yet), unless we restrict ourselves to the core feature set. Embedded HTML is not markdown (by definition), and as such almost never portable. In your case two options might be worth considering: - contribute a patch for gitea's markdown renderer to support the markdown flavor you have in mind, or, - Generate proper HTML where you can use all formatting and publish it via https://pages.codeberg.org
hw commented 4 weeks ago
Owner

@6543 :

gitea v1.11.0 will close this

Should be fixed by now. Can you please test?

@6543 : > gitea v1.11.0 will close this Should be fixed by now. Can you please test?
Booteille commented 4 weeks ago
Poster

@6543 :

gitea v1.11.0 will close this

Should be fixed by now. Can you please test?

Yup. It is fixed now.

Just a thing. Are you able to use keyboard shortcuts like Ctrl+B? It seems I can't. (I am using Firefox Nightly 74.0a1 2020-01-28 on Linux Mint)

> @6543 : > > > gitea v1.11.0 will close this > > Should be fixed by now. Can you please test? > Yup. It is fixed now. Just a thing. Are you able to use keyboard shortcuts like Ctrl+B? It seems I can't. (I am using Firefox Nightly 74.0a1 2020-01-28 on Linux Mint)
hw commented 3 weeks ago
Owner

Yes, working here. An issue with the nightly browser snapshot best reported to the Firefox team?

Yes, working here. An issue with the nightly browser snapshot best reported to the Firefox team?
Sign in to join this conversation.
No Milestone
No Assignees
5 Participants
Due Date

No due date set.

Dependencies

This issue currently doesn't have any dependencies.

Loading…
Cancel
Save
There is no content yet.