test_bug172261.html starts failing after moving content/html/ to dom/html/

NEW
Unassigned

Status

()

P5
normal
5 years ago
7 months ago

People

(Reporter: poiru, Unassigned)

Tracking

Trunk
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

5 years ago
In a try push involving the move of content/html to dom/html (bug 946065), the following test failure popped up:

21:50:28     INFO -  3550 INFO TEST-START | /tests/dom/html/test/test_bug172261.html
21:50:28     INFO -  3551 INFO dumping last 22 message(s)
...
21:50:28     INFO -  3570 INFO TEST-PASS | /tests/dom/html/test/test_bug172261.html | label control should be null if the id in @for              is empty
21:50:28     INFO -  3571 INFO TEST-PASS | /tests/dom/html/test/test_bug172261.html | out of document label shouldn't    labelze a form control
...
21:50:28     INFO -  3575 INFO TEST-UNEXPECTED-ERROR | /tests/dom/html/test/test_bug172261.html | /tests/dom/html/test/forms/test_label_control_attribute.html - finished in a non-clean fashion, probably because it didn't call SimpleTest.finish()

Even though test_bug172261.html causes the test failure, the actual test messages (e.g. "label control should be null if the id...") are from test_label_control_attribute.html, which completed shortly before test_bug172261.html. The use of `history.back()`/`history.forward()` in test_bug172261.html probably has something to do with this.

See try push: https://tbpl.mozilla.org/?tree=Try&rev=e3a74f2ee973
(Reporter)

Comment 1

5 years ago
bz, since you wrote this test, do you happen to have any idea about what is going on?
Flags: needinfo?(bzbarsky)
Not offhand.  Is the back() or forward() perhaps navigating the test frame itself instead of the subframe it should be navigating?
Flags: needinfo?(bzbarsky)
https://bugzilla.mozilla.org/show_bug.cgi?id=1472046

Move all DOM bugs that haven’t been updated in more than 3 years and has no one currently assigned to P5.

If you have questions, please contact :mdaly.
Priority: -- → P5
You need to log in before you can comment on or make changes to this bug.