Add integration points for WebDriver BiDi load scripts #8300
Conversation
db3f039 to
962814e
Compare
|
This might be too early, for the navigation/traversal case. At the point these scripts run, there will be no DOM at all, besides the The DOM only gets created inside the various "page load processing model for..." sections, e.g. in the parser for HTML or for text files, or synthetically for media. |
|
"No DOM at all apart from the Document object" is more or less what's required; if you want access to some specific part of the document to work on you can register a mutation observer or similar; it's not expected that people will directly try to do DOM manipulation in the top level script. But the hard requirement is that it runs before any script on the page (similar to Web Extensions content scripts). |
962814e to
28044ae
Compare
These scripts are intended to run early in the Document lifecycle, before any content scripts have run. The actual running of the scripts is defined in the WebDriver BiDi specification, so HTML just needs to call to the relevant algorithm at the correct point in the document lifecycle.
28044ae to
6353b85
Compare
These scripts are intended to run early in the Document lifecycle, before any content scripts have run. The actual running of the scripts is defined in the WebDriver BiDi specification, so HTML just needs to call to the relevant algorithm at the correct point in the document lifecycle.
(See WHATWG Working Mode: Changes for more details.)
/document-lifecycle.html ( diff )
/document-sequences.html ( diff )
/infrastructure.html ( diff )