Open
Bug 1571990
Opened 5 years ago
Updated 2 years ago
Unload event test failure - navigation timing followup
Categories
(Core :: DOM: Core & HTML, defect, P3)
Tracking
()
NEW
Tracking | Status | |
---|---|---|
firefox-esr60 | --- | affected |
firefox-esr68 | --- | unaffected |
firefox68 | --- | unaffected |
firefox69 | --- | unaffected |
firefox70 | --- | unaffected |
People
(Reporter: cfogel, Unassigned)
References
Details
Attachments
(1 file)
**Follow up for bug 1560495;
Affected versions
- esr 60.9.0 /60.8.0
Affected platforms
- Windows 10, Ubuntu 16.04, macOS 10.14;
Steps to reproduce
- Access http://w3c-test.org/navigation-timing/unload-event-same-origin-check.html
- wait for all tests to pass.
Expected result
- all tests pass
Actual result
- test Failing:
Fail No previous document with same origin redirect assert_equals: Expected redirectCount to be 1 expected 1 but got 0
run_test@http://w3c-test.org/navigation-timing/unload-event-same-origin-check.html:101:17
create_test/<@http://w3c-test.org/navigation-timing/unload-event-same-origin-check.html:108:25
Regression range
- not a regression, according to Will's assessment the test never passed;
Additional notes
- issue fixed on 1560495 for 69.0b10, esr68.1.0, 70.0a1 (2019-08-04);
Updated•5 years ago
|
Priority: -- → P3
Comment 2•5 years ago
|
||
Hi Will,
Is this issue simply about test failure in esr60? If so, I wonder what the priority is and would we really consider to uplift it to esr60? Would you mind clarifying more?
Flags: needinfo?(whawkins)
Comment 3•5 years ago
|
||
Sorry a response was so long in coming ... I have a proposed patch that I submitting for feedback that, I hope, correctly resolves this problem.
Will
Comment 4•5 years ago
|
||
Updated•5 years ago
|
Assignee: nobody → whawkins
Updated•5 years ago
|
Flags: needinfo?(whawkins)
Updated•4 years ago
|
Assignee: whawkins → nobody
Updated•2 years ago
|
Severity: normal → S3
You need to log in
before you can comment on or make changes to this bug.
Description
•