Closed
Bug 112557
Opened 24 years ago
Closed 24 years ago
Should be a more visible note to NOT include full HTML source in bug reports.
Categories
(Bugzilla :: Bugzilla-General, defect)
Tracking
()
RESOLVED
FIXED
Bugzilla old
People
(Reporter: caillon, Assigned: gerv)
Details
We've all seen them, users who try to be helpful and submit the full HTML for us
to view. However, it really is annoying because everytime we open the bug, we
have to PgDown to get past the 1000 line HTML. Granted, there is no foolproof
way to prevent it, but perhaps a more visible note would work.
The current text (in the additional information section) is:
Add any additional information you feel may be relevant to this bug, such as a
few lines of HTML that demonstrate the problem, a Talkback crash ID, or special
information about your computer's configuration.
I propose that be changed to something like:
Add any additional information you feel may be relevant to this bug, such as a a
Talkback crash ID, special information about your computer's configuration, or a
<strong>few lines</strong> of HTML that demonstrate the problem. <span
style="color: red">Please do not paste the full HTML source in the comments. If
you wish to include the <em>full</em> HTML source, please use the "Create
Attachment" link on your bug after it has been posted.</span>
| Reporter | ||
Comment 1•24 years ago
|
||
Just to clarify my original comments, which on second reading sound a bit
awkward, I want a more visible note to include the full HTML source as an
attachment opposed to inline in the comments.
Comment 2•24 years ago
|
||
Added a note about this on bug #109311.
| Assignee | ||
Comment 3•24 years ago
|
||
Done.
Gerv
Status: NEW → RESOLVED
Closed: 24 years ago
Resolution: --- → FIXED
Comment 4•23 years ago
|
||
Webtools/Bugzilla Helper is being retired.
Component: Bugzilla Helper → Bugzilla-General
Product: Webtools → Bugzilla
Target Milestone: --- → Bugzilla old
Version: other → unspecified
Updated•13 years ago
|
QA Contact: matty_is_a_geek → default-qa
You need to log in
before you can comment on or make changes to this bug.
Description
•