Useful bug reports are ones that get bugs fixed.
If an engineer can't see it or conclusively prove that it exists, the engineer will probably stamp it "WORKSFORME" or "INVALID", and move on to the next bug.
The quicker the engineer can trace down the issue to a specific problem, the more likely it'll be fixed expediently.
Figure out exactly what the problem is.
Figure out exactly how to fix the problem.
Explain the bug in clear and specific terms.
Prepend "[REG]" to the summary for a regression bug.
"Drag-selecting any page crashes Mac builds in NSGetFactory"
Explain the bug to the developer with a more detailed explanation.
State the problem behavior.
Be as specific as possible.
Identify the simplest steps needed to reproduce the bug.
Show developer what is wrong.
Describe what actually happened.
Describe what should have happened.
Pinpoint the bug.
Rip out everything in the page that isn't required to reproduce the bug.
Try variations on the test case to find related situations that also trigger the bug.
Web pages might change or disappear. Attachments do not.
Select the software version, the platform and the OS version that this bug occurred on.
Crash data (backtrace), Screenshot, ...
[CASCADE]author !important rules override user !important rules in user.css
!important style rules in the author stylesheet override !important style rules in the user stylesheet ([profile]/chrome/user.css); a direct contradiction of the CSS spec (CSS2:6.4)
Steps to Reproduce:
1.) Copy 'Sample user.css' to the 'chrome' subdirectory in your profile directory for Mozilla. Rename it to 'user.css'.
2.) View 'Testcase' in Mozilla.
* Both to be attached shortly
Tested with build id=2000061720 on Windows 2000
Audio tests use video element
Below audio tests use <video> element:
Bug Triage is a process to:
Bug Triage Team: