2030909 - browsingContext.reload fails for frames

Status: NEW

(Remote Protocol :: WebDriver BiDi, defect, P2)

Description

[Julian Descottes [:jdescottes]]

I was looking at Bug 2028075 to see if it could quickly be fixed, but the command actually fails on our side.

It fails regardless of the value of the wait parameter. We detect that the browsing context is discarded and fail the navigation:

E       webdriver.bidi.error.UnknownErrorException: unknown error (Error: Browsing context got discarded)
E       
E       Remote-end stacktrace:
E       
E       #onNavigationFailed@chrome://remote/content/shared/Navigate.sys.mjs:404:26
E       emit@resource://gre/modules/EventEmitter.sys.mjs:156:19
E       #forwardEvent@chrome://remote/content/shared/listeners/NavigationListener.sys.mjs:91:10
E       emit@resource://gre/modules/EventEmitter.sys.mjs:156:19
E       #onNavigationEvent@chrome://remote/content/shared/NavigationManager.sys.mjs:1025:10
E       emit@resource://gre/modules/EventEmitter.sys.mjs:156:19
E       notifyNavigationFailed@chrome://remote/content/shared/NavigationManager.sys.mjs:438:10
E       notifyNavigationFailed@chrome://remote/content/shared/NavigationManager.sys.mjs:934:29
E       #onContextDiscarded@chrome://remote/content/shared/NavigationManager.sys.mjs:750:27
E       emit@resource://gre/modules/EventEmitter.sys.mjs:156:19
E       observe@chrome://remote/content/shared/listeners/BrowsingContextListener.sys.mjs:84:14

This doesn't happen for navigations, so I'm suspecting that calling context.sessionHistory.reload triggers this with non top-level contexts?

I tried to revert back to context.reload, and in that case the reload commands "succeeds", but instead of reloading the frame to the same URL, it navigates it to about:blank...