Use waitForNewTab instead of progress listener in addJsonViewTab
Categories
(DevTools :: JSON Viewer, enhancement)
Tracking
(firefox61 fixed)
Tracking | Status | |
---|---|---|
firefox61 | --- | fixed |
People
(Reporter: Oriol, Assigned: Oriol)
References
Details
Attachments
(2 files, 1 obsolete file)
Comment hidden (mozreview-request) |
Comment hidden (mozreview-request) |
Comment 3•7 years ago
|
||
Comment hidden (mozreview-request) |
Assignee | ||
Updated•7 years ago
|
Assignee | ||
Comment 5•7 years ago
|
||
Comment 6•7 years ago
|
||
mozreview-review |
Assignee | ||
Updated•7 years ago
|
![]() |
||
Comment 8•7 years ago
|
||
bugherder |
Updated•7 years ago
|
![]() |
||
Comment 9•5 years ago
|
||
I'm not sure I understand this change. Now we're racing two separate tab loads against each other and using whichever one happens to return back to us first? Why do we do that?
Assignee | ||
Comment 10•5 years ago
|
||
If I remember correctly, the test browser_jsonview_content_type.js uses some invalid content types. Some of them just trigger a download instead of loading anything, and then one of these promises didn't resolve. And the other promise also had some problems in other cases, like resolving too late or something. So I decided to use them both.
![]() |
||
Comment 11•5 years ago
|
||
OK, then this code should probably document exactly what it's doing and why, since it's doing two very different loads with different conditions on resolving and then just using whichever of them resolves first, as if it did not matter what the conditions are, etc...
Comment 12•5 years ago
|
||
@Oriol: can you please file a follow up and provide detailed comment that explains the logic, thanks!
Honza
Description
•