Open Bug 2041412 Opened 1 month ago

Review side-effects on content page from WebDriver serialization logic

Categories

(Remote Protocol :: WebDriver BiDi, task, P3)

Product:
Remote Protocol
Component:
WebDriver BiDi
Type:
task

Tracking

(Not tracked)

People

(Reporter: jdescottes, Unassigned)

References

Details

From https://phabricator.services.mozilla.com/D288831?id=1263891#inline-1617357

Is it meaningful to mention in a code comment this will make the debugger visible to the web page?
The serialization may easily trigger JS code of the page, which may trigger breakpoints in unexpected ways.

As far as I know the serialization performed in the moz:debugging module is similar to the one we use in the rest of BiDi, so we should follow up here and check is our serialization logic is susceptible to trigger content JS and be detected by the content page.

You need to log in before you can comment on or make changes to this bug.