test_timer.js uses unknown Services member properties
Categories
(Firefox :: General, defect)
Tracking
()
People
(Reporter: standard8, Assigned: farre)
References
(Regression)
Details
(Keywords: regression)
Attachments
(1 file)
In test_timer.js there are a couple of accesses of Services.mainThreadEventTarget
, however that is not available on Services
and should probably be Services.tm.mainThreadEventTarget
.
If this is fixed or not, it does not affect the test passing, which also makes me wonder if the test is actually testing what bug 1384041 intended it to test.
Updated•3 years ago
|
Comment 1•3 years ago
|
||
Set release status flags based on info from the regressing bug 1384041
Updated•3 years ago
|
Updated•3 years ago
|
Updated•3 years ago
|
Comment 2•3 years ago
|
||
Is this test even testing anything important anymore?
Assignee | ||
Comment 3•3 years ago
|
||
So, the main thread event target is the default target, I think. So no, it probably doesn't.
Updated•3 years ago
|
Reporter | ||
Comment 4•3 years ago
|
||
(In reply to Andreas Farre [:farre] from comment #3)
So, the main thread event target is the default target, I think. So no, it probably doesn't.
Should the whole test file be removed, or only parts of it?
Assignee | ||
Updated•2 years ago
|
Assignee | ||
Comment 5•2 years ago
|
||
These test were intended to use the planned, but dropped, one thread
per TabGroup feature. They used to dispatch timer callbacks to the
system group to test the labelling needed, but since TabGroups were
removed and the event target was changed to the main thread event
target, these tests actually test the same thing as the regular
non-target tests. This because nsITimer is created with a target which
just happens to be the mainThreadEventTarget.
Comment 7•2 years ago
|
||
bugherder |
Updated•2 years ago
|
Description
•