Closed
Bug 707479
Opened 13 years ago
Closed 13 years ago
HTML tags and entities are visible in tool tips for in-litmus and in-testsuite
Categories
(bugzilla.mozilla.org :: General, defect)
Tracking
()
RESOLVED
FIXED
People
(Reporter: nn.dm55, Unassigned)
Details
Attachments
(1 file)
126.10 KB,
image/png
|
Details |
User Agent: Mozilla/5.0 (X11; Linux i686 on x86_64; rv:9.0) Gecko/20100101 Firefox/9.0 Build ID: 20111130065942 Steps to reproduce: I went to https://bugzilla.mozilla.org/show_bug.cgi?id=595934. I was curious what the flags meant, so I moved the mouse over in-testsuite. The in-litmus flag also has the same problem. Actual results: For in-testsuite, a tool tip was shown saying "Whether the bug has a testcase in the test suite or not. Set it to "in-testsuite?" if the bug needs a testcase (only set this if the bug actually <em>needs</em> a testcase — not all bugs do, even layout bugs!), set it to "in-testsuite+" if the bug has an appropriate testcase, and set it to "in-testsuite-" if the bug doesn't need an explicit testcase (e.g. for code cleanup bugs). Only QA actively working on test cases in the component should use this keyword" Expected results: "Needs" should have been bold, and the mdash HTML entity should have become a dash.
Comment 1•13 years ago
|
||
I have updated the text description for the flags to remove the HTML entities entirely as Bugzilla is not coded to allow HTML entities for flag descriptions. We do allow them for product, component, and group descriptions where they have more value such as (more info) type links, etc. Upstream does not allow HTML entities for flag descriptions, and I don't see a reason to allow them for BMO at this time either due to I don't feel they give any real value here. Changing from the upstream would mean yet another customization we would have to forward maintain as well. dkl
Status: UNCONFIRMED → RESOLVED
Closed: 13 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•