Don't emit navigation events when creating new top-level browsing contexts (tabs) when "about:blank" is loaded
Categories
(Remote Protocol :: WebDriver BiDi, enhancement, P2)
Tracking
(Not tracked)
People
(Reporter: whimboo, Unassigned)
References
()
Details
(Whiteboard: [webdriver:m13])
Attachments
(1 file)
When executing the command browsingContext.create
we currently send out navigation events like browsingContext.navigationStarted
even for the initial about:blank
. As discussed during TPAC (https://github.com/w3c/webdriver-bidi/issues/766) we should align to other browsers and as well follow the HTML specification which doesn't say that navigation events should be emitted.
This should also apply to evaluating a script that runs window.open()
for about:blank
.
But normal navigations to about:blank
should not be affected.
@whimboo So webdriver bidi, I see the constructor for browsingContext
emits the nnavigationStarted
event, which is a private method. The browsingContext.Create
doesn't emit the navigationStarted
event itself. So what we are trying to do here is to remove this right?
Updated•20 days ago
|
Updated•18 days ago
|
Comment 3•16 days ago
|
||
Per discussion on phabricator, resetting the bug
Updated•10 days ago
|
Reporter | ||
Updated•10 days ago
|
Description
•