refreshTab now uses BrowserTestUtils.loadURI which has differences with gBrowser.reloadTab
Categories
(DevTools :: Framework, task)
Tracking
(firefox91 fixed)
| Tracking | Status | |
|---|---|---|
| firefox91 | --- | fixed |
People
(Reporter: nchevobbe, Assigned: nchevobbe)
References
Details
Attachments
(1 file)
In Bug 1714920, I'm trying to replace the usage of testActor.reload with refreshTab, but one test is failing:
In /browser_inspector_highlighter-06.js#23-24 the page does not keep the scroll position when "reloading" anymore.
My hunch is that since refreshTab uses loadURI to navigate, we're hitting a different path than with an actual reload.
In order to make refreshTab more reliable, we should keep using gBrowser.reloadTab.
|
Assignee | |
Comment 1•3 years ago
|
||
In Bug 1710582, refreshTab switched to use navigateTo in order to handle target switching.
The catch is that navigateTo uses BrowserTestUtils.loadURI, which triggers a slightly
different behavior than gBrowser.reloadTab (for example, it does not keep the scroll position).
This patch introduces a new option in navigateTo where the consumer choose how
the navigation occurs, and we make refreshTab use gBrowser.reloadTab.
|
||
Updated•3 years ago
|
Pushed by nchevobbe@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/effb13df8fcd [devtools] Use gBrowser.reloadTab in navigateTo when the provided URL is the same as the current one. r=ochameau.
|
||
Comment 3•3 years ago
|
||
| bugherder | ||
Description
•