On Fri, Oct 16, 2020 at 4:49 AM Konstantin Tokarev <[email protected]> wrote: > > > Why would you want to do that? > > I think rich text in comments is evil, for the same reasons as HTML e-mail. > > Yes, with markdown you won't often see unreadably colored text (what happens > with HTML e-mail), but still there is pretty much room for abuse of formatting > (to attract attention or just because they can), or accidental formatting when > non-markdown text is interpreted as markdown resulting in a total mess > (which inexperienced users cannot fix and leave as is). > > BTW, GitHub recently added rich text UI controls to code review comments, so > even those who don't know markdown can start abusing formatting there now...
Sorry, I'm not sure about that why you feel a bad emotion for rich text format... As my stance, I prefer to display a code snippet, quote and list as formatted style with a discussion with BTS. It's a bit hard to read a quote as styled `>` like this text email for me, so I'd like to read a quote block as a styled format by default. But this is my personal complaints. I would not like to say that WebKit Bugzilla must support markdown in the comment form immediately. -- Tetsuharu OHZEKI [email protected] On Fri, Oct 16, 2020 at 4:49 AM Konstantin Tokarev <[email protected]> wrote: > > > > 14.10.2020, 16:52, "Tetsuharu OHZEKI" <[email protected]>: > > I feel from this discussion that everybody has their own best way and > > we’re tackling to resolve them at once in this migration process. > > I also feel it’s a bit difficult to conclude something. > > > > FWIW, I would like to write some my problems about the current > > workflow to help figure out > > what is a problem in the current workflow and what we should be > > resolved in this or other future process. > > > > This would not propose an actual solution, but I believe this would > > help to find a final solution and other people will also say your > > problems to help. > > > > 1. Code review tools > > WebKit Bugzilla’s code review tool is not a beautiful solution for today. > > I would like to get a preview for markdown file or syntax highlights. > > > > 2. Bug Tracking System > > I don’t feel a problem to use WebKit Bugzilla, and I doubt that using > > Bugzilla is really a problem to collect a feedback from the webdev > > community as other people said in this thread. > > However, I have some complaints… > > > > * I’d like to write markdown as a comment for bugs. > > Why would you want to do that? > > I think rich text in comments is evil, for the same reasons as HTML e-mail. > > Yes, with markdown you won't often see unreadably colored text (what happens > with HTML e-mail), but still there is pretty much room for abuse of formatting > (to attract attention or just because they can), or accidental formatting when > non-markdown text is interpreted as markdown resulting in a total mess > (which inexperienced users cannot fix and leave as is). > > BTW, GitHub recently added rich text UI controls to code review comments, so > even those who don't know markdown can start abusing formatting there now... > > -- > Regards, > Konstantin _______________________________________________ webkit-dev mailing list [email protected] https://lists.webkit.org/mailman/listinfo/webkit-dev
