Open
Bug 1175403
Opened 9 years ago
Updated 4 years ago
Split fullscreen and pointer lock test sets into separate tests
Categories
(Core :: DOM: Core & HTML, defect, P5)
Core
DOM: Core & HTML
Tracking
()
NEW
Tracking | Status | |
---|---|---|
firefox41 | --- | affected |
People
(Reporter: xidorn, Unassigned)
Details
Currently, all pointer lock tests are included in an all-in-one mochitest test_pointerlock-api.html. This makes the message from treeherder really unhelpful, and from time to time, causes the whole test set be disabled in most platforms because some of the tests inside have frequent intermittent failures.
We should split them into separate tests, so that we can toggle them individually, and allow them to run on as many platforms as possible.
Reporter | ||
Comment 1•9 years ago
|
||
Tests for fullscreen API have the same problem.
Summary: Split pointer lock test set into separate tests → Split fullscreen and pointer lock test sets into separate tests
Comment 2•4 years ago
|
||
Bulk-downgrade of unassigned, >=5 years untouched DOM/Storage bugs' priority.
If you have reason to believe this is wrong (especially for the severity), please write a comment and ni :jstutte.
Severity: normal → S4
Priority: -- → P5
You need to log in
before you can comment on or make changes to this bug.
Description
•