Wait for navigation-committed event for navigation to error page
Categories
(Remote Protocol :: WebDriver BiDi, defect, P3)
Tracking
(firefox148 fixed, firefox149 fixed)
People
(Reporter: jdescottes, Assigned: jdescottes)
References
Details
(Whiteboard: [webdriver:m19][webdriver:relnote])
Attachments
(2 files)
|
48 bytes,
text/x-phabricator-request
|
Details | Review | |
|
48 bytes,
text/x-phabricator-request
|
phab-bot
:
approval-mozilla-beta+
|
Details | Review |
See Bug 1984535. In case of a navigation which redirects to an error page, the document might not be ready when resolving because we currently resolve immediately on location change.
Instead we should wait for navigation-committed. Although we need to be careful to wait for the correct navigation committed event, because we might already have received one for the original URL (before the error redirect).
| Assignee | ||
Comment 1•1 month ago
|
||
When a navigation redirects to an error page we should still wait for the navigation committed
event to make sure the document is ready to be used.
Updated•1 month ago
|
| Assignee | ||
Updated•1 month ago
|
Comment 4•1 month ago
|
||
firefox-beta Uplift Approval Request
- User impact if declined: Frequent intermittents tracked in Bug 1984535
- Code covered by automated testing: yes
- Fix verified in Nightly: yes
- Needs manual QE test: no
- Steps to reproduce for manual QE testing: N/A
- Risk associated with taking this patch: low
- Explanation of risk level: WebDriver BiDi only, and only updating the logic related to navigations which lead to an error page.
- String changes made/needed: N/A
- Is Android affected?: yes
| Assignee | ||
Comment 5•1 month ago
|
||
When a navigation redirects to an error page we should still wait for the navigation committed
event to make sure the document is ready to be used.
Original Revision: https://phabricator.services.mozilla.com/D281390
Updated•1 month ago
|
Updated•1 month ago
|
Updated•18 days ago
|
Description
•