Add WebDriver BiDi network logging with stable request IDs #1860
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR is based on the feedback on the existing PR #1540 as well as what was discussed in w3c/webdriver-bidi#722
This introduces the concept of a stable webdriver id for requests, which is consistent across redirects, authentication attempts and CORS preflight.
This also triggers steps from the webdriver bidi specification to emit network events and trigger data collection mecanisms.
Preview | Diff