https://bugs.kde.org/show_bug.cgi?id=513647
Bug ID: 513647
Summary: Support markup at KDE BZ
Classification: Websites
Product: bugs.kde.org
Version First unspecified
Reported In:
Platform: unspecified
URL: https://discuss.kde.org/t/comment-formatting-on-bugs-k
de-org/14699/8?u=rokejulianlockhart
OS: All
Status: REPORTED
Severity: wishlist
Priority: NOR
Component: code customizations
Assignee: [email protected]
Reporter: [email protected]
CC: [email protected]
Target Milestone: ---
Created attachment 187842
--> https://bugs.kde.org/attachment.cgi?id=187842&action=edit
A Duplicate Of `bugzilla.kernel.org/show_bug.cgi?id=220181#c5`
# SUMMARY
Please provide markup syntax for KDE Bugzilla.
# STEPS TO REPRODUCE / RATIONALE
When authoring a bug report, many authors frequently reference inline code,
short (block) sections of logs, diffs, and code; and they quote documentation.
Although some basic use cases can be bypassed with solely UTF characters, like
the keycap character in replacement for `<kbd>`, and the tabular for
multi-paragraph lists, the aforementioned use cases are impossible to fulfill
without a layer of abstraction.
You may believe that this would require Mozilla's Bugzilla customisations
(Harmony). However, it doesn't, as my comment at
https://bugzilla.kernel.org/show_bug.cgi?id=220181#c5 demonstrates.
# OBSERVED RESULT
I am able to write `blockquote`s and `pre`s, but because these are combined,
even this isn't semantic for a screen reader, and means that quotations must be
manually truncated, lest they render off the display. This doesn't work when
reading on a smartphone, nor when quoting code.
# EXPECTED RESULT
I should be able to write in a markup language that supports more than merely
Bugzilla's conflation of HTML5's `blockquote` and `pre`.
# ADDITIONAL INFORMATION
Discussed at:
-
https://discuss.kde.org/t/comment-formatting-on-bugs-kde-org/14699/8?u=rokejulianlockhart
- https://bugs.kde.org/show_bug.cgi?id=502960#c25
- https://bugs.kde.org/show_bug.cgi?id=501276#c8
Another example exists, from another user – where I first observed that hashes
before headings were acceptable – but I haven't been able to locate it since.
--
You are receiving this mail because:
You are watching all bug changes.
