https://wiki.mozilla.org/api.php?action=feedcontributions&user=Whimboo&feedformat=atomMozillaWiki - User contributions [en]2024-03-29T10:17:55ZUser contributionsMediaWiki 1.27.4https://wiki.mozilla.org/index.php?title=WebDriver/RemoteProtocol/WebDriver_BiDi&diff=1249329WebDriver/RemoteProtocol/WebDriver BiDi2024-01-05T10:02:06Z<p>Whimboo: </p>
<hr />
<div>[https://w3c.github.io/webdriver-bidi WebDriver BiDi] is an extension of the [https://w3c.github.io/webdriver/ WebDriver specification] that offers a bidirectional communication between a webdriver compatible client and a remote end like Firefox. That means that beside sending commands to the browser and receiving responses, it will be also possible to register for certain events (e.g page load, network interception).<br />
<br />
== Product Backlog Status ==<br />
* [https://bugzilla.mozilla.org/buglist.cgi?f1=status_whiteboard&v1=%5Bwebdriver%3Abacklog&query_format=advanced&o1=substring Full Product Backlog]<br />
<br />
== Milestones ==<br />
<br />
=== WebDriver BiDi Milestone 10 - In Development ===<br />
'''Goal''': TODO<br />
<br />
'''Details''': [[WebDriver/RemoteProtocol/WebDriver_BiDi/Milestone_10|Milestone 10 status]]<br />
<br />
=== WebDriver BiDi Milestone 9 - Completed December 24th, 2023 ===<br />
'''Goal''': Milestone 9 maintains its focus on aligning and integrating essential functionalities from Puppeteer and Selenium. Although we managed to implement most of these high-priority features in Milestone 8, some pending APIs still need to be integrated before Puppeteer can formally announce WebDriver BiDi support for Firefox. In our dedication to staying synchronized with Selenium, we're also addressing their top priorities. As a result, this milestone is dedicated to empowering clients to introduce new features and products to their users through WebDriver BiDi.<br />
<br />
'''Details''': [[WebDriver/RemoteProtocol/WebDriver_BiDi/Milestone_9|Milestone 9 status]]<br />
<br />
=== WebDriver BiDi Milestone 8 - Completed October 01st, 2023 ===<br />
'''Goal''': Milestone 8 is centered around matching and integrating crucial features from Puppeteer and Selenium. This milestone is all about enabling those clients to ship features and products using WebDriver BiDi to their users. By doing so, we hope to encourage a continuous flow of valuable user feedback and collect success narratives. This feedback is crucial for the ongoing improvement and evolution of the WebDriver BiDi project, enabling us to better align with the needs and expectations of our user base.<br />
<br />
'''Details''': [[WebDriver/RemoteProtocol/WebDriver_BiDi/Milestone_8|Milestone 8 status]]<br />
<br />
=== WebDriver BiDi Milestone 7 - Completed July 02nd, 2023 ===<br />
'''Goal''': This milestone aims to expand the set of APIs supported for creating basic automated tests using WebDriver BiDi. The newly added APIs will include support for HTTP authentication, improved user interaction with pages and prompts. Additionally, efforts will be made to maintain our infrastructure for the existing WebDriver based test suites.<br />
<br />
'''Details''': [[WebDriver/RemoteProtocol/WebDriver_BiDi/Milestone_7|Milestone 7 status]]<br />
<br />
=== WebDriver BiDi Milestone 6 - Completed April 9th, 2023 ===<br />
'''Goal''': Support a minimal set of APIs for creating basic automated tests using WebDriver BiDi.<br />
<br />
'''Details''': [[WebDriver/RemoteProtocol/WebDriver_BiDi/Milestone_6|Milestone 6 status]]<br />
<br />
=== WebDriver BiDi Milestone 5 - Completed January 15th, 2023 ===<br />
'''Goal''': Support required network and page events for HAR file generation.<br />
<br />
'''Details''': [[WebDriver/RemoteProtocol/WebDriver_BiDi/Milestone_5|Milestone 5 status]]<br />
<br />
=== WebDriver BiDi Milestone 4 - Completed September 20th, 2022 ===<br />
'''Goal''': Support evaluating remote scripts, and passing javascript data between the browser and the client and vice-versa.<br />
<br />
'''Details''': [[WebDriver/RemoteProtocol/WebDriver_BiDi/Milestone_4|Milestone 4 status]]<br />
<br />
=== WebDriver BiDi Milestone 3 - Completed May 15th, 2022 ===<br />
'''Goal''': Basic support for the browsingContext.navigate command, and collaboration with the Selenium project to get log.entryAdded support added.<br />
<br />
'''Details''': [[WebDriver/RemoteProtocol/WebDriver_BiDi/Milestone_3|Milestone 3 status]]<br />
<br />
=== WebDriver BiDi Milestone 2 - Completed December 19th, 2021 ===<br />
'''Goal''': Extend the current WebDriver BiDi code base to fully support log.entryAdded events and allow clients to unsubscribe from this event.<br />
<br />
'''Details''': [[WebDriver/RemoteProtocol/WebDriver_BiDi/Milestone_2|Milestone 2 status]]<br />
<br />
=== WebDriver BiDi Milestone 1 - Completed September 10th, 2021 ===<br />
'''Goal''': Adapt the existing Remote Agent code base, and make it ready for building support for WebDriver BiDi. Introduce support for basic logging events (plain string message).<br />
<br />
'''Details''': [[WebDriver/RemoteProtocol/WebDriver_BiDi/Milestone_1|Milestone 1 status]]</div>Whimboohttps://wiki.mozilla.org/index.php?title=WebDriver/RemoteProtocol/WebDriver_BiDi&diff=1249328WebDriver/RemoteProtocol/WebDriver BiDi2024-01-05T09:55:29Z<p>Whimboo: /* WebDriver BiDi Milestone 10 - Not started */</p>
<hr />
<div>[https://w3c.github.io/webdriver-bidi WebDriver BiDi] is an extension of the [https://w3c.github.io/webdriver/ WebDriver specification] that offers a bidirectional communication between a webdriver compatible client and a remote end like Firefox. That means that beside sending commands to the browser and receiving responses, it will be also possible to register for certain events (e.g page load, network interception).<br />
<br />
== Product Backlog Status ==<br />
* [https://bugzilla.mozilla.org/buglist.cgi?f1=status_whiteboard&v1=%5Bwebdriver%3Abacklog&query_format=advanced&o1=substring Full Product Backlog]<br />
<br />
== Milestones ==<br />
<br />
=== WebDriver BiDi Milestone 10 - Active ===<br />
'''Goal''': TODO<br />
<br />
'''Details''': [[WebDriver/RemoteProtocol/WebDriver_BiDi/Milestone_10|Milestone 10 status]]<br />
<br />
=== WebDriver BiDi Milestone 9 - Completed December 24th, 2023 ===<br />
'''Goal''': Milestone 9 maintains its focus on aligning and integrating essential functionalities from Puppeteer and Selenium. Although we managed to implement most of these high-priority features in Milestone 8, some pending APIs still need to be integrated before Puppeteer can formally announce WebDriver BiDi support for Firefox. In our dedication to staying synchronized with Selenium, we're also addressing their top priorities. As a result, this milestone is dedicated to empowering clients to introduce new features and products to their users through WebDriver BiDi.<br />
<br />
'''Details''': [[WebDriver/RemoteProtocol/WebDriver_BiDi/Milestone_9|Milestone 9 status]]<br />
<br />
=== WebDriver BiDi Milestone 8 - Completed October 01st, 2023 ===<br />
'''Goal''': Milestone 8 is centered around matching and integrating crucial features from Puppeteer and Selenium. This milestone is all about enabling those clients to ship features and products using WebDriver BiDi to their users. By doing so, we hope to encourage a continuous flow of valuable user feedback and collect success narratives. This feedback is crucial for the ongoing improvement and evolution of the WebDriver BiDi project, enabling us to better align with the needs and expectations of our user base.<br />
<br />
'''Details''': [[WebDriver/RemoteProtocol/WebDriver_BiDi/Milestone_8|Milestone 8 status]]<br />
<br />
=== WebDriver BiDi Milestone 7 - Completed July 02nd, 2023 ===<br />
'''Goal''': This milestone aims to expand the set of APIs supported for creating basic automated tests using WebDriver BiDi. The newly added APIs will include support for HTTP authentication, improved user interaction with pages and prompts. Additionally, efforts will be made to maintain our infrastructure for the existing WebDriver based test suites.<br />
<br />
'''Details''': [[WebDriver/RemoteProtocol/WebDriver_BiDi/Milestone_7|Milestone 7 status]]<br />
<br />
=== WebDriver BiDi Milestone 6 - Completed April 9th, 2023 ===<br />
'''Goal''': Support a minimal set of APIs for creating basic automated tests using WebDriver BiDi.<br />
<br />
'''Details''': [[WebDriver/RemoteProtocol/WebDriver_BiDi/Milestone_6|Milestone 6 status]]<br />
<br />
=== WebDriver BiDi Milestone 5 - Completed January 15th, 2023 ===<br />
'''Goal''': Support required network and page events for HAR file generation.<br />
<br />
'''Details''': [[WebDriver/RemoteProtocol/WebDriver_BiDi/Milestone_5|Milestone 5 status]]<br />
<br />
=== WebDriver BiDi Milestone 4 - Completed September 20th, 2022 ===<br />
'''Goal''': Support evaluating remote scripts, and passing javascript data between the browser and the client and vice-versa.<br />
<br />
'''Details''': [[WebDriver/RemoteProtocol/WebDriver_BiDi/Milestone_4|Milestone 4 status]]<br />
<br />
=== WebDriver BiDi Milestone 3 - Completed May 15th, 2022 ===<br />
'''Goal''': Basic support for the browsingContext.navigate command, and collaboration with the Selenium project to get log.entryAdded support added.<br />
<br />
'''Details''': [[WebDriver/RemoteProtocol/WebDriver_BiDi/Milestone_3|Milestone 3 status]]<br />
<br />
=== WebDriver BiDi Milestone 2 - Completed December 19th, 2021 ===<br />
'''Goal''': Extend the current WebDriver BiDi code base to fully support log.entryAdded events and allow clients to unsubscribe from this event.<br />
<br />
'''Details''': [[WebDriver/RemoteProtocol/WebDriver_BiDi/Milestone_2|Milestone 2 status]]<br />
<br />
=== WebDriver BiDi Milestone 1 - Completed September 10th, 2021 ===<br />
'''Goal''': Adapt the existing Remote Agent code base, and make it ready for building support for WebDriver BiDi. Introduce support for basic logging events (plain string message).<br />
<br />
'''Details''': [[WebDriver/RemoteProtocol/WebDriver_BiDi/Milestone_1|Milestone 1 status]]</div>Whimboohttps://wiki.mozilla.org/index.php?title=WebDriver/RemoteProtocol/WebDriver_BiDi&diff=1249278WebDriver/RemoteProtocol/WebDriver BiDi2023-12-27T11:59:50Z<p>Whimboo: </p>
<hr />
<div>[https://w3c.github.io/webdriver-bidi WebDriver BiDi] is an extension of the [https://w3c.github.io/webdriver/ WebDriver specification] that offers a bidirectional communication between a webdriver compatible client and a remote end like Firefox. That means that beside sending commands to the browser and receiving responses, it will be also possible to register for certain events (e.g page load, network interception).<br />
<br />
== Product Backlog Status ==<br />
* [https://bugzilla.mozilla.org/buglist.cgi?f1=status_whiteboard&v1=%5Bwebdriver%3Abacklog&query_format=advanced&o1=substring Full Product Backlog]<br />
<br />
== Milestones ==<br />
<br />
=== WebDriver BiDi Milestone 10 - Not started ===<br />
'''Goal''': TODO<br />
<br />
'''Details''': [[WebDriver/RemoteProtocol/WebDriver_BiDi/Milestone_10|Milestone 10 status]]<br />
<br />
=== WebDriver BiDi Milestone 9 - Completed December 24th, 2023 ===<br />
'''Goal''': Milestone 9 maintains its focus on aligning and integrating essential functionalities from Puppeteer and Selenium. Although we managed to implement most of these high-priority features in Milestone 8, some pending APIs still need to be integrated before Puppeteer can formally announce WebDriver BiDi support for Firefox. In our dedication to staying synchronized with Selenium, we're also addressing their top priorities. As a result, this milestone is dedicated to empowering clients to introduce new features and products to their users through WebDriver BiDi.<br />
<br />
'''Details''': [[WebDriver/RemoteProtocol/WebDriver_BiDi/Milestone_9|Milestone 9 status]]<br />
<br />
=== WebDriver BiDi Milestone 8 - Completed October 01, 2023 ===<br />
'''Goal''': Milestone 8 is centered around matching and integrating crucial features from Puppeteer and Selenium. This milestone is all about enabling those clients to ship features and products using WebDriver BiDi to their users. By doing so, we hope to encourage a continuous flow of valuable user feedback and collect success narratives. This feedback is crucial for the ongoing improvement and evolution of the WebDriver BiDi project, enabling us to better align with the needs and expectations of our user base.<br />
<br />
'''Details''': [[WebDriver/RemoteProtocol/WebDriver_BiDi/Milestone_8|Milestone 8 status]]<br />
<br />
=== WebDriver BiDi Milestone 7 - Completed July 02, 2023 ===<br />
'''Goal''': This milestone aims to expand the set of APIs supported for creating basic automated tests using WebDriver BiDi. The newly added APIs will include support for HTTP authentication, improved user interaction with pages and prompts. Additionally, efforts will be made to maintain our infrastructure for the existing WebDriver based test suites.<br />
<br />
'''Details''': [[WebDriver/RemoteProtocol/WebDriver_BiDi/Milestone_7|Milestone 7 status]]<br />
<br />
=== WebDriver BiDi Milestone 6 - Completed April 9th, 2023 ===<br />
'''Goal''': Support a minimal set of APIs for creating basic automated tests using WebDriver BiDi.<br />
<br />
'''Details''': [[WebDriver/RemoteProtocol/WebDriver_BiDi/Milestone_6|Milestone 6 status]]<br />
<br />
=== WebDriver BiDi Milestone 5 - Completed January 15th, 2023 ===<br />
'''Goal''': Support required network and page events for HAR file generation.<br />
<br />
'''Details''': [[WebDriver/RemoteProtocol/WebDriver_BiDi/Milestone_5|Milestone 5 status]]<br />
<br />
=== WebDriver BiDi Milestone 4 - Completed September 20th, 2022 ===<br />
'''Goal''': Support evaluating remote scripts, and passing javascript data between the browser and the client and vice-versa.<br />
<br />
'''Details''': [[WebDriver/RemoteProtocol/WebDriver_BiDi/Milestone_4|Milestone 4 status]]<br />
<br />
=== WebDriver BiDi Milestone 3 - Completed May 15th, 2022 ===<br />
'''Goal''': Basic support for the browsingContext.navigate command, and collaboration with the Selenium project to get log.entryAdded support added.<br />
<br />
'''Details''': [[WebDriver/RemoteProtocol/WebDriver_BiDi/Milestone_3|Milestone 3 status]]<br />
<br />
=== WebDriver BiDi Milestone 2 - Completed December 19th, 2021 ===<br />
'''Goal''': Extend the current WebDriver BiDi code base to fully support log.entryAdded events and allow clients to unsubscribe from this event.<br />
<br />
'''Details''': [[WebDriver/RemoteProtocol/WebDriver_BiDi/Milestone_2|Milestone 2 status]]<br />
<br />
=== WebDriver BiDi Milestone 1 - Completed September 10th, 2021 ===<br />
'''Goal''': Adapt the existing Remote Agent code base, and make it ready for building support for WebDriver BiDi. Introduce support for basic logging events (plain string message).<br />
<br />
'''Details''': [[WebDriver/RemoteProtocol/WebDriver_BiDi/Milestone_1|Milestone 1 status]]</div>Whimboohttps://wiki.mozilla.org/index.php?title=WebDriver/RemoteProtocol/WebDriver_BiDi&diff=1249277WebDriver/RemoteProtocol/WebDriver BiDi2023-12-27T11:59:16Z<p>Whimboo: Milestone 9 completed</p>
<hr />
<div>[https://w3c.github.io/webdriver-bidi WebDriver BiDi] is an extension of the [https://w3c.github.io/webdriver/ WebDriver specification] that offers a bidirectional communication between a webdriver compatible client and a remote end like Firefox. That means that beside sending commands to the browser and receiving responses, it will be also possible to register for certain events (e.g page load, network interception).<br />
<br />
== Product Backlog Status ==<br />
* [https://bugzilla.mozilla.org/buglist.cgi?f1=status_whiteboard&v1=%5Bwebdriver%3Abacklog&query_format=advanced&o1=substring Full Product Backlog]<br />
<br />
== Milestones ==<br />
<br />
=== WebDriver BiDi Milestone 10 - Not started ===<br />
'''Goal''': TODO<br />
<br />
'''Details''': [[WebDriver/RemoteProtocol/WebDriver_BiDi/Milestone_10|Milestone 10 status]]<br />
<br />
=== WebDriver BiDi Milestone 9 - Completed ===<br />
'''Goal''': Milestone 9 maintains its focus on aligning and integrating essential functionalities from Puppeteer and Selenium. Although we managed to implement most of these high-priority features in Milestone 8, some pending APIs still need to be integrated before Puppeteer can formally announce WebDriver BiDi support for Firefox. In our dedication to staying synchronized with Selenium, we're also addressing their top priorities. As a result, this milestone is dedicated to empowering clients to introduce new features and products to their users through WebDriver BiDi.<br />
<br />
'''Details''': [[WebDriver/RemoteProtocol/WebDriver_BiDi/Milestone_9|Milestone 9 status]]<br />
<br />
=== WebDriver BiDi Milestone 8 - Completed October 01, 2023 ===<br />
'''Goal''': Milestone 8 is centered around matching and integrating crucial features from Puppeteer and Selenium. This milestone is all about enabling those clients to ship features and products using WebDriver BiDi to their users. By doing so, we hope to encourage a continuous flow of valuable user feedback and collect success narratives. This feedback is crucial for the ongoing improvement and evolution of the WebDriver BiDi project, enabling us to better align with the needs and expectations of our user base.<br />
<br />
'''Details''': [[WebDriver/RemoteProtocol/WebDriver_BiDi/Milestone_8|Milestone 8 status]]<br />
<br />
=== WebDriver BiDi Milestone 7 - Completed July 02, 2023 ===<br />
'''Goal''': This milestone aims to expand the set of APIs supported for creating basic automated tests using WebDriver BiDi. The newly added APIs will include support for HTTP authentication, improved user interaction with pages and prompts. Additionally, efforts will be made to maintain our infrastructure for the existing WebDriver based test suites.<br />
<br />
'''Details''': [[WebDriver/RemoteProtocol/WebDriver_BiDi/Milestone_7|Milestone 7 status]]<br />
<br />
=== WebDriver BiDi Milestone 6 - Completed April 9th, 2023 ===<br />
'''Goal''': Support a minimal set of APIs for creating basic automated tests using WebDriver BiDi.<br />
<br />
'''Details''': [[WebDriver/RemoteProtocol/WebDriver_BiDi/Milestone_6|Milestone 6 status]]<br />
<br />
=== WebDriver BiDi Milestone 5 - Completed January 15th, 2023 ===<br />
'''Goal''': Support required network and page events for HAR file generation.<br />
<br />
'''Details''': [[WebDriver/RemoteProtocol/WebDriver_BiDi/Milestone_5|Milestone 5 status]]<br />
<br />
=== WebDriver BiDi Milestone 4 - Completed September 20th, 2022 ===<br />
'''Goal''': Support evaluating remote scripts, and passing javascript data between the browser and the client and vice-versa.<br />
<br />
'''Details''': [[WebDriver/RemoteProtocol/WebDriver_BiDi/Milestone_4|Milestone 4 status]]<br />
<br />
=== WebDriver BiDi Milestone 3 - Completed May 15th, 2022 ===<br />
'''Goal''': Basic support for the browsingContext.navigate command, and collaboration with the Selenium project to get log.entryAdded support added.<br />
<br />
'''Details''': [[WebDriver/RemoteProtocol/WebDriver_BiDi/Milestone_3|Milestone 3 status]]<br />
<br />
=== WebDriver BiDi Milestone 2 - Completed December 19th, 2021 ===<br />
'''Goal''': Extend the current WebDriver BiDi code base to fully support log.entryAdded events and allow clients to unsubscribe from this event.<br />
<br />
'''Details''': [[WebDriver/RemoteProtocol/WebDriver_BiDi/Milestone_2|Milestone 2 status]]<br />
<br />
=== WebDriver BiDi Milestone 1 - Completed September 10th, 2021 ===<br />
'''Goal''': Adapt the existing Remote Agent code base, and make it ready for building support for WebDriver BiDi. Introduce support for basic logging events (plain string message).<br />
<br />
'''Details''': [[WebDriver/RemoteProtocol/WebDriver_BiDi/Milestone_1|Milestone 1 status]]</div>Whimboohttps://wiki.mozilla.org/index.php?title=WebDriver/RemoteProtocol/WebDriver_BiDi/Milestone_9&diff=1249276WebDriver/RemoteProtocol/WebDriver BiDi/Milestone 92023-12-27T11:58:45Z<p>Whimboo: Completed</p>
<hr />
<div>= WebDriver BiDi Milestone 9 - Completed =<br />
'''Goal''': Milestone 9 maintains its focus on aligning and integrating essential functionalities from Puppeteer and Selenium. Although we managed to implement most of these high-priority features in Milestone 8, some pending APIs still need to be integrated before Puppeteer can formally announce WebDriver BiDi support for Firefox. In our dedication to staying synchronized with Selenium, we're also addressing their top priorities. As a result, this milestone is dedicated to empowering clients to introduce new features and products to their users through WebDriver BiDi.<br />
<br />
'''Progress''':<br />
* [https://1drv.ms/x/s!AuFRYG6dkmv15064mFWJg7L-vR4N?e=JOPZ7y Tracking dashboard]<br />
<br />
'''Updates''':<br />
* [https://drive.google.com/drive/folders/1BgvtSImr9YYVTbu1YREgsX-AfZOlIuQL?usp=drive_link Weekly Status Updates]<br />
<br />
'''Queries''':<br />
* [https://bugzilla.mozilla.org/buglist.cgi?resolution=---&resolution=FIXED&o1=substring&f1=status_whiteboard&query_format=advanced&v1=%5Bwebdriver%3Am9 All Bugs]<br />
* [https://bugzilla.mozilla.org/buglist.cgi?v1=%5Bwebdriver%3Am9&f1=status_whiteboard&resolution=---&o1=substring&query_format=advanced&bug_status=UNCONFIRMED&bug_status=NEW Available Bugs]<br />
* [https://bugzilla.mozilla.org/buglist.cgi?resolution=---&bug_status=ASSIGNED&bug_status=REOPENED&v1=%5Bwebdriver%3Am9&query_format=advanced&f1=status_whiteboard&o1=substring Assigned Bugs]<br />
* [https://bugzilla.mozilla.org/buglist.cgi?f1=status_whiteboard&resolution=FIXED&query_format=advanced&o1=substring&v1=%5Bwebdriver%3Am9 Completed Bugs]<br />
<br />
'''Milestone Backlog''':<br />
<bugzilla><br />
{<br />
"whiteboard": "[webdriver:m9",<br />
"include_fields":"id, summary, status, assigned_to, cf_fx_points"<br />
}<br />
</bugzilla></div>Whimboohttps://wiki.mozilla.org/index.php?title=WebDriver/RemoteProtocol/WebDriver_BiDi/Milestone_10&diff=1249256WebDriver/RemoteProtocol/WebDriver BiDi/Milestone 102023-12-19T20:55:09Z<p>Whimboo: Initial content</p>
<hr />
<div>= WebDriver BiDi Milestone 10 - Not Started =<br />
'''Goal''': TODO<br />
<br />
'''Progress''':<br />
* [ Tracking dashboard]<br />
<br />
'''Updates''':<br />
* [ Weekly Status Updates]<br />
<br />
'''Queries''':<br />
* [https://bugzilla.mozilla.org/buglist.cgi?resolution=---&resolution=FIXED&o1=substring&f1=status_whiteboard&query_format=advanced&v1=%5Bwebdriver%3Am10 All Bugs]<br />
* [https://bugzilla.mozilla.org/buglist.cgi?f1=status_whiteboard&resolution=---&o1=substring&query_format=advanced&bug_status=UNCONFIRMED&bug_status=NEW&v1=%5Bwebdriver%3Am10 Available Bugs]<br />
* [https://bugzilla.mozilla.org/buglist.cgi?resolution=---&bug_status=ASSIGNED&bug_status=REOPENED&query_format=advanced&f1=status_whiteboard&o1=substring&v1=%5Bwebdriver%3Am10 Assigned Bugs]<br />
* [https://bugzilla.mozilla.org/buglist.cgi?f1=status_whiteboard&resolution=FIXED&query_format=advanced&o1=substring&v1=%5Bwebdriver%3Am10 Completed Bugs]<br />
<br />
'''Milestone Backlog''':<br />
<bugzilla><br />
{<br />
"whiteboard": "[webdriver:m10",<br />
"include_fields":"id, summary, status, assigned_to, cf_fx_points"<br />
}<br />
</bugzilla></div>Whimboohttps://wiki.mozilla.org/index.php?title=WebDriver/RemoteProtocol/WebDriver_BiDi&diff=1249255WebDriver/RemoteProtocol/WebDriver BiDi2023-12-19T20:52:37Z<p>Whimboo: Adding milestone 10</p>
<hr />
<div>[https://w3c.github.io/webdriver-bidi WebDriver BiDi] is an extension of the [https://w3c.github.io/webdriver/ WebDriver specification] that offers a bidirectional communication between a webdriver compatible client and a remote end like Firefox. That means that beside sending commands to the browser and receiving responses, it will be also possible to register for certain events (e.g page load, network interception).<br />
<br />
== Product Backlog Status ==<br />
* [https://bugzilla.mozilla.org/buglist.cgi?f1=status_whiteboard&v1=%5Bwebdriver%3Abacklog&query_format=advanced&o1=substring Full Product Backlog]<br />
<br />
== Milestones ==<br />
<br />
=== WebDriver BiDi Milestone 10 - Not started ===<br />
'''Goal''': TODO<br />
<br />
'''Details''': [[WebDriver/RemoteProtocol/WebDriver_BiDi/Milestone_10|Milestone 10 status]]<br />
<br />
=== WebDriver BiDi Milestone 9 - In Development ===<br />
'''Goal''': Milestone 9 maintains its focus on aligning and integrating essential functionalities from Puppeteer and Selenium. Although we managed to implement most of these high-priority features in Milestone 8, some pending APIs still need to be integrated before Puppeteer can formally announce WebDriver BiDi support for Firefox. In our dedication to staying synchronized with Selenium, we're also addressing their top priorities. As a result, this milestone is dedicated to empowering clients to introduce new features and products to their users through WebDriver BiDi.<br />
<br />
'''Details''': [[WebDriver/RemoteProtocol/WebDriver_BiDi/Milestone_9|Milestone 9 status]]<br />
<br />
=== WebDriver BiDi Milestone 8 - Completed October 01, 2023 ===<br />
'''Goal''': Milestone 8 is centered around matching and integrating crucial features from Puppeteer and Selenium. This milestone is all about enabling those clients to ship features and products using WebDriver BiDi to their users. By doing so, we hope to encourage a continuous flow of valuable user feedback and collect success narratives. This feedback is crucial for the ongoing improvement and evolution of the WebDriver BiDi project, enabling us to better align with the needs and expectations of our user base.<br />
<br />
'''Details''': [[WebDriver/RemoteProtocol/WebDriver_BiDi/Milestone_8|Milestone 8 status]]<br />
<br />
=== WebDriver BiDi Milestone 7 - Completed July 02, 2023 ===<br />
'''Goal''': This milestone aims to expand the set of APIs supported for creating basic automated tests using WebDriver BiDi. The newly added APIs will include support for HTTP authentication, improved user interaction with pages and prompts. Additionally, efforts will be made to maintain our infrastructure for the existing WebDriver based test suites.<br />
<br />
'''Details''': [[WebDriver/RemoteProtocol/WebDriver_BiDi/Milestone_7|Milestone 7 status]]<br />
<br />
=== WebDriver BiDi Milestone 6 - Completed April 9th, 2023 ===<br />
'''Goal''': Support a minimal set of APIs for creating basic automated tests using WebDriver BiDi.<br />
<br />
'''Details''': [[WebDriver/RemoteProtocol/WebDriver_BiDi/Milestone_6|Milestone 6 status]]<br />
<br />
=== WebDriver BiDi Milestone 5 - Completed January 15th, 2023 ===<br />
'''Goal''': Support required network and page events for HAR file generation.<br />
<br />
'''Details''': [[WebDriver/RemoteProtocol/WebDriver_BiDi/Milestone_5|Milestone 5 status]]<br />
<br />
=== WebDriver BiDi Milestone 4 - Completed September 20th, 2022 ===<br />
'''Goal''': Support evaluating remote scripts, and passing javascript data between the browser and the client and vice-versa.<br />
<br />
'''Details''': [[WebDriver/RemoteProtocol/WebDriver_BiDi/Milestone_4|Milestone 4 status]]<br />
<br />
=== WebDriver BiDi Milestone 3 - Completed May 15th, 2022 ===<br />
'''Goal''': Basic support for the browsingContext.navigate command, and collaboration with the Selenium project to get log.entryAdded support added.<br />
<br />
'''Details''': [[WebDriver/RemoteProtocol/WebDriver_BiDi/Milestone_3|Milestone 3 status]]<br />
<br />
=== WebDriver BiDi Milestone 2 - Completed December 19th, 2021 ===<br />
'''Goal''': Extend the current WebDriver BiDi code base to fully support log.entryAdded events and allow clients to unsubscribe from this event.<br />
<br />
'''Details''': [[WebDriver/RemoteProtocol/WebDriver_BiDi/Milestone_2|Milestone 2 status]]<br />
<br />
=== WebDriver BiDi Milestone 1 - Completed September 10th, 2021 ===<br />
'''Goal''': Adapt the existing Remote Agent code base, and make it ready for building support for WebDriver BiDi. Introduce support for basic logging events (plain string message).<br />
<br />
'''Details''': [[WebDriver/RemoteProtocol/WebDriver_BiDi/Milestone_1|Milestone 1 status]]</div>Whimboohttps://wiki.mozilla.org/index.php?title=WebDriver/RemoteProtocol/WebDriver_BiDi/Milestone_6&diff=1249117WebDriver/RemoteProtocol/WebDriver BiDi/Milestone 62023-12-01T13:24:03Z<p>Whimboo: fix bugzilla query</p>
<hr />
<div>= WebDriver BiDi Milestone 6 - Completed April 9th, 2023 =<br />
'''Goal''': Support a minimal set of APIs for creating basic automated tests using WebDriver BiDi.<br />
<br />
'''Progress''':<br />
* [https://1drv.ms/x/s!AuFRYG6dkmv150g5Bdy788QhPzqi?e=i7KBQZ Tracking dashboard]<br />
<br />
'''Updates''':<br />
* [https://drive.google.com/drive/folders/1sBMQ-7l-6pp15lkNXJc64xwo4IuoKFaF?usp=sharing Status Update Archive]<br />
<br />
'''Milestone Backlog''':<br />
<bugzilla><br />
{<br />
"whiteboard": "[webdriver:m6]",<br />
"priority":["P1"], <br />
"include_fields":"id, summary, status, assigned_to, priority, cf_fx_points"<br />
}<br />
</bugzilla></div>Whimboohttps://wiki.mozilla.org/index.php?title=WebDriver/RemoteProtocol/WebDriver_BiDi/Milestone_9&diff=1248199WebDriver/RemoteProtocol/WebDriver BiDi/Milestone 92023-09-29T10:23:27Z<p>Whimboo: Adding the goal</p>
<hr />
<div>= WebDriver BiDi Milestone 9 - In Development =<br />
'''Goal''': Milestone 9 maintains its focus on aligning and integrating essential functionalities from Puppeteer and Selenium. Although we managed to implement most of these high-priority features in Milestone 8, some pending APIs still need to be integrated before Puppeteer can formally announce WebDriver BiDi support for Firefox. In our dedication to staying synchronized with Selenium, we're also addressing their top priorities. As a result, this milestone is dedicated to empowering clients to introduce new features and products to their users through WebDriver BiDi.<br />
<br />
'''Progress''':<br />
* [Tracking dashboard]<br />
<br />
'''Updates''':<br />
* [Weekly Status Updates]<br />
<br />
'''Queries''':<br />
* [https://bugzilla.mozilla.org/buglist.cgi?columnlist=opendate%2Ccf_last_resolved%2Cshort_desc%2Ccomponent%2Cassigned_to%2Cbug_status%2Cresolution%2Ckeywords%2Cstatus_whiteboard%2Cpriority%2Ccf_fx_points&f1=status_whiteboard&o1=substring&resolution=---&resolution=FIXED&order=bug_status%2Cpriority%2Cassigned_to%2Cbug_id&list_id=16736761&v1=%5Bwebdriver%3Am9 All Bugs]<br />
* [https://bugzilla.mozilla.org/buglist.cgi?bug_status=UNCONFIRMED&bug_status=NEW&columnlist=opendate%2Ccf_last_resolved%2Cshort_desc%2Ccomponent%2Cassigned_to%2Cbug_status%2Cresolution%2Ckeywords%2Cstatus_whiteboard%2Cpriority%2Ccf_fx_points&f1=status_whiteboard&o1=substring&resolution=---&order=bug_status%2Cpriority%2Cassigned_to%2Cbug_id&list_id=16736763&v1=webdriver%3Am9 Available Bugs]<br />
* [https://bugzilla.mozilla.org/buglist.cgi?bug_status=ASSIGNED&bug_status=REOPENED&columnlist=opendate%2Ccf_last_resolved%2Cshort_desc%2Ccomponent%2Cassigned_to%2Cbug_status%2Cresolution%2Ckeywords%2Cstatus_whiteboard%2Cpriority%2Ccf_fx_points&f1=status_whiteboard&o1=substring&resolution=---&order=bug_status%2Cpriority%2Cassigned_to%2Cbug_id&list_id=16736765&v1=webdriver%3Am9 Assigned Bugs]<br />
* [https://bugzilla.mozilla.org/buglist.cgi?columnlist=opendate%2Ccf_last_resolved%2Cshort_desc%2Ccomponent%2Cassigned_to%2Cbug_status%2Cresolution%2Ckeywords%2Cstatus_whiteboard%2Cpriority%2Ccf_fx_points&f1=status_whiteboard&o1=substring&resolution=FIXED&order=bug_status%2Cpriority%2Cassigned_to%2Cbug_id&list_id=16736766&v1=webdriver%3Am9 Completed Bugs]<br />
<br />
'''Milestone Backlog''':<br />
<bugzilla><br />
{<br />
"whiteboard": "[webdriver:m9",<br />
"include_fields":"id, summary, status, assigned_to, cf_fx_points"<br />
}<br />
</bugzilla></div>Whimboohttps://wiki.mozilla.org/index.php?title=WebDriver/RemoteProtocol/WebDriver_BiDi&diff=1248198WebDriver/RemoteProtocol/WebDriver BiDi2023-09-29T10:23:04Z<p>Whimboo: /* WebDriver BiDi Milestone 9 - Not started */ Adding the goal</p>
<hr />
<div>[https://w3c.github.io/webdriver-bidi WebDriver BiDi] is an extension of the [https://w3c.github.io/webdriver/ WebDriver specification] that offers a bidirectional communication between a webdriver compatible client and a remote end like Firefox. That means that beside sending commands to the browser and receiving responses, it will be also possible to register for certain events (e.g page load, network interception).<br />
<br />
== Product Backlog Status ==<br />
* [https://mzl.la/3crgUad Milestone 9 Candidates (P2)]<br />
* [https://mzl.la/3Rok3pN Future Candidates (P3)]<br />
* [https://mzl.la/3Awn6Wg Full Product Backlog (P2 & P3)]<br />
<br />
== Milestones ==<br />
<br />
=== WebDriver BiDi Milestone 9 - Not started ===<br />
'''Goal''': Milestone 9 maintains its focus on aligning and integrating essential functionalities from Puppeteer and Selenium. Although we managed to implement most of these high-priority features in Milestone 8, some pending APIs still need to be integrated before Puppeteer can formally announce WebDriver BiDi support for Firefox. In our dedication to staying synchronized with Selenium, we're also addressing their top priorities. As a result, this milestone is dedicated to empowering clients to introduce new features and products to their users through WebDriver BiDi.<br />
<br />
'''Details''': [[WebDriver/RemoteProtocol/WebDriver_BiDi/Milestone_9|Milestone 9 status]]<br />
<br />
=== WebDriver BiDi Milestone 8 - In Development ===<br />
'''Goal''': Milestone 8 is centered around matching and integrating crucial features from Puppeteer and Selenium. This milestone is all about enabling those clients to ship features and products using WebDriver BiDi to their users. By doing so, we hope to encourage a continuous flow of valuable user feedback and collect success narratives. This feedback is crucial for the ongoing improvement and evolution of the WebDriver BiDi project, enabling us to better align with the needs and expectations of our user base.<br />
<br />
'''Details''': [[WebDriver/RemoteProtocol/WebDriver_BiDi/Milestone_8|Milestone 8 status]]<br />
<br />
=== WebDriver BiDi Milestone 7 - Completed July 02, 2023 ===<br />
'''Goal''': This milestone aims to expand the set of APIs supported for creating basic automated tests using WebDriver BiDi. The newly added APIs will include support for HTTP authentication, improved user interaction with pages and prompts. Additionally, efforts will be made to maintain our infrastructure for the existing WebDriver based test suites.<br />
<br />
'''Details''': [[WebDriver/RemoteProtocol/WebDriver_BiDi/Milestone_7|Milestone 7 status]]<br />
<br />
=== WebDriver BiDi Milestone 6 - Completed April 9th, 2023 ===<br />
'''Goal''': Support a minimal set of APIs for creating basic automated tests using WebDriver BiDi.<br />
<br />
'''Details''': [[WebDriver/RemoteProtocol/WebDriver_BiDi/Milestone_6|Milestone 6 status]]<br />
<br />
=== WebDriver BiDi Milestone 5 - Completed January 15th, 2023 ===<br />
'''Goal''': Support required network and page events for HAR file generation.<br />
<br />
'''Details''': [[WebDriver/RemoteProtocol/WebDriver_BiDi/Milestone_5|Milestone 5 status]]<br />
<br />
=== WebDriver BiDi Milestone 4 - Completed September 20th, 2022 ===<br />
'''Goal''': Support evaluating remote scripts, and passing javascript data between the browser and the client and vice-versa.<br />
<br />
'''Details''': [[WebDriver/RemoteProtocol/WebDriver_BiDi/Milestone_4|Milestone 4 status]]<br />
<br />
=== WebDriver BiDi Milestone 3 - Completed May 15th, 2022 ===<br />
'''Goal''': Basic support for the browsingContext.navigate command, and collaboration with the Selenium project to get log.entryAdded support added.<br />
<br />
'''Details''': [[WebDriver/RemoteProtocol/WebDriver_BiDi/Milestone_3|Milestone 3 status]]<br />
<br />
=== WebDriver BiDi Milestone 2 - Completed December 19th, 2021 ===<br />
'''Goal''': Extend the current WebDriver BiDi code base to fully support log.entryAdded events and allow clients to unsubscribe from this event.<br />
<br />
'''Details''': [[WebDriver/RemoteProtocol/WebDriver_BiDi/Milestone_2|Milestone 2 status]]<br />
<br />
=== WebDriver BiDi Milestone 1 - Completed September 10th, 2021 ===<br />
'''Goal''': Adapt the existing Remote Agent code base, and make it ready for building support for WebDriver BiDi. Introduce support for basic logging events (plain string message).<br />
<br />
'''Details''': [[WebDriver/RemoteProtocol/WebDriver_BiDi/Milestone_1|Milestone 1 status]]</div>Whimboohttps://wiki.mozilla.org/index.php?title=WebDriver/RemoteProtocol/WebDriver_BiDi/Milestone_9&diff=1248180WebDriver/RemoteProtocol/WebDriver BiDi/Milestone 92023-09-28T11:44:40Z<p>Whimboo: remove closing brackets</p>
<hr />
<div>= WebDriver BiDi Milestone 9 - In Development =<br />
'''Goal''': TODO<br />
<br />
'''Progress''':<br />
* [Tracking dashboard]<br />
<br />
'''Updates''':<br />
* [Weekly Status Updates]<br />
<br />
'''Queries''':<br />
* [https://bugzilla.mozilla.org/buglist.cgi?columnlist=opendate%2Ccf_last_resolved%2Cshort_desc%2Ccomponent%2Cassigned_to%2Cbug_status%2Cresolution%2Ckeywords%2Cstatus_whiteboard%2Cpriority%2Ccf_fx_points&f1=status_whiteboard&o1=substring&resolution=---&resolution=FIXED&order=bug_status%2Cpriority%2Cassigned_to%2Cbug_id&list_id=16736761&v1=%5Bwebdriver%3Am9 All Bugs]<br />
* [https://bugzilla.mozilla.org/buglist.cgi?bug_status=UNCONFIRMED&bug_status=NEW&columnlist=opendate%2Ccf_last_resolved%2Cshort_desc%2Ccomponent%2Cassigned_to%2Cbug_status%2Cresolution%2Ckeywords%2Cstatus_whiteboard%2Cpriority%2Ccf_fx_points&f1=status_whiteboard&o1=substring&resolution=---&order=bug_status%2Cpriority%2Cassigned_to%2Cbug_id&list_id=16736763&v1=webdriver%3Am9 Available Bugs]<br />
* [https://bugzilla.mozilla.org/buglist.cgi?bug_status=ASSIGNED&bug_status=REOPENED&columnlist=opendate%2Ccf_last_resolved%2Cshort_desc%2Ccomponent%2Cassigned_to%2Cbug_status%2Cresolution%2Ckeywords%2Cstatus_whiteboard%2Cpriority%2Ccf_fx_points&f1=status_whiteboard&o1=substring&resolution=---&order=bug_status%2Cpriority%2Cassigned_to%2Cbug_id&list_id=16736765&v1=webdriver%3Am9 Assigned Bugs]<br />
* [https://bugzilla.mozilla.org/buglist.cgi?columnlist=opendate%2Ccf_last_resolved%2Cshort_desc%2Ccomponent%2Cassigned_to%2Cbug_status%2Cresolution%2Ckeywords%2Cstatus_whiteboard%2Cpriority%2Ccf_fx_points&f1=status_whiteboard&o1=substring&resolution=FIXED&order=bug_status%2Cpriority%2Cassigned_to%2Cbug_id&list_id=16736766&v1=webdriver%3Am9 Completed Bugs]<br />
<br />
'''Milestone Backlog''':<br />
<bugzilla><br />
{<br />
"whiteboard": "[webdriver:m9",<br />
"include_fields":"id, summary, status, assigned_to, cf_fx_points"<br />
}<br />
</bugzilla></div>Whimboohttps://wiki.mozilla.org/index.php?title=WebDriver/RemoteProtocol/WebDriver_BiDi/Milestone_9&diff=1248179WebDriver/RemoteProtocol/WebDriver BiDi/Milestone 92023-09-28T11:43:48Z<p>Whimboo: New milestone 9</p>
<hr />
<div>= WebDriver BiDi Milestone 9 - In Development =<br />
'''Goal''': TODO<br />
<br />
'''Progress''':<br />
* [Tracking dashboard]<br />
<br />
'''Updates''':<br />
* [Weekly Status Updates]<br />
<br />
'''Queries''':<br />
* [https://bugzilla.mozilla.org/buglist.cgi?columnlist=opendate%2Ccf_last_resolved%2Cshort_desc%2Ccomponent%2Cassigned_to%2Cbug_status%2Cresolution%2Ckeywords%2Cstatus_whiteboard%2Cpriority%2Ccf_fx_points&f1=status_whiteboard&o1=substring&resolution=---&resolution=FIXED&order=bug_status%2Cpriority%2Cassigned_to%2Cbug_id&list_id=16736761&v1=%5Bwebdriver%3Am9 All Bugs]<br />
* [https://bugzilla.mozilla.org/buglist.cgi?bug_status=UNCONFIRMED&bug_status=NEW&columnlist=opendate%2Ccf_last_resolved%2Cshort_desc%2Ccomponent%2Cassigned_to%2Cbug_status%2Cresolution%2Ckeywords%2Cstatus_whiteboard%2Cpriority%2Ccf_fx_points&f1=status_whiteboard&o1=substring&resolution=---&order=bug_status%2Cpriority%2Cassigned_to%2Cbug_id&list_id=16736763&v1=webdriver%3Am9 Available Bugs]<br />
* [https://bugzilla.mozilla.org/buglist.cgi?bug_status=ASSIGNED&bug_status=REOPENED&columnlist=opendate%2Ccf_last_resolved%2Cshort_desc%2Ccomponent%2Cassigned_to%2Cbug_status%2Cresolution%2Ckeywords%2Cstatus_whiteboard%2Cpriority%2Ccf_fx_points&f1=status_whiteboard&o1=substring&resolution=---&order=bug_status%2Cpriority%2Cassigned_to%2Cbug_id&list_id=16736765&v1=webdriver%3Am9] Assigned Bugs]<br />
* [https://bugzilla.mozilla.org/buglist.cgi?columnlist=opendate%2Ccf_last_resolved%2Cshort_desc%2Ccomponent%2Cassigned_to%2Cbug_status%2Cresolution%2Ckeywords%2Cstatus_whiteboard%2Cpriority%2Ccf_fx_points&f1=status_whiteboard&o1=substring&resolution=FIXED&order=bug_status%2Cpriority%2Cassigned_to%2Cbug_id&list_id=16736766&v1=webdriver%3Am9] Completed Bugs]<br />
<br />
'''Milestone Backlog''':<br />
<bugzilla><br />
{<br />
"whiteboard": "[webdriver:m9",<br />
"include_fields":"id, summary, status, assigned_to, cf_fx_points"<br />
}<br />
</bugzilla></div>Whimboohttps://wiki.mozilla.org/index.php?title=WebDriver/RemoteProtocol/WebDriver_BiDi&diff=1248146WebDriver/RemoteProtocol/WebDriver BiDi2023-09-26T11:34:53Z<p>Whimboo: Added milestone 9</p>
<hr />
<div>[https://w3c.github.io/webdriver-bidi WebDriver BiDi] is an extension of the [https://w3c.github.io/webdriver/ WebDriver specification] that offers a bidirectional communication between a webdriver compatible client and a remote end like Firefox. That means that beside sending commands to the browser and receiving responses, it will be also possible to register for certain events (e.g page load, network interception).<br />
<br />
== Product Backlog Status ==<br />
* [https://mzl.la/3crgUad Milestone 9 Candidates (P2)]<br />
* [https://mzl.la/3Rok3pN Future Candidates (P3)]<br />
* [https://mzl.la/3Awn6Wg Full Product Backlog (P2 & P3)]<br />
<br />
== Milestones ==<br />
<br />
=== WebDriver BiDi Milestone 9 - Not started ===<br />
'''Goal''': TODO<br />
<br />
'''Details''': [[WebDriver/RemoteProtocol/WebDriver_BiDi/Milestone_9|Milestone 9 status]]<br />
<br />
=== WebDriver BiDi Milestone 8 - In Development ===<br />
'''Goal''': Milestone 8 is centered around matching and integrating crucial features from Puppeteer and Selenium. This milestone is all about enabling those clients to ship features and products using WebDriver BiDi to their users. By doing so, we hope to encourage a continuous flow of valuable user feedback and collect success narratives. This feedback is crucial for the ongoing improvement and evolution of the WebDriver BiDi project, enabling us to better align with the needs and expectations of our user base.<br />
<br />
'''Details''': [[WebDriver/RemoteProtocol/WebDriver_BiDi/Milestone_8|Milestone 8 status]]<br />
<br />
=== WebDriver BiDi Milestone 7 - Completed July 02, 2023 ===<br />
'''Goal''': This milestone aims to expand the set of APIs supported for creating basic automated tests using WebDriver BiDi. The newly added APIs will include support for HTTP authentication, improved user interaction with pages and prompts. Additionally, efforts will be made to maintain our infrastructure for the existing WebDriver based test suites.<br />
<br />
'''Details''': [[WebDriver/RemoteProtocol/WebDriver_BiDi/Milestone_7|Milestone 7 status]]<br />
<br />
=== WebDriver BiDi Milestone 6 - Completed April 9th, 2023 ===<br />
'''Goal''': Support a minimal set of APIs for creating basic automated tests using WebDriver BiDi.<br />
<br />
'''Details''': [[WebDriver/RemoteProtocol/WebDriver_BiDi/Milestone_6|Milestone 6 status]]<br />
<br />
=== WebDriver BiDi Milestone 5 - Completed January 15th, 2023 ===<br />
'''Goal''': Support required network and page events for HAR file generation.<br />
<br />
'''Details''': [[WebDriver/RemoteProtocol/WebDriver_BiDi/Milestone_5|Milestone 5 status]]<br />
<br />
=== WebDriver BiDi Milestone 4 - Completed September 20th, 2022 ===<br />
'''Goal''': Support evaluating remote scripts, and passing javascript data between the browser and the client and vice-versa.<br />
<br />
'''Details''': [[WebDriver/RemoteProtocol/WebDriver_BiDi/Milestone_4|Milestone 4 status]]<br />
<br />
=== WebDriver BiDi Milestone 3 - Completed May 15th, 2022 ===<br />
'''Goal''': Basic support for the browsingContext.navigate command, and collaboration with the Selenium project to get log.entryAdded support added.<br />
<br />
'''Details''': [[WebDriver/RemoteProtocol/WebDriver_BiDi/Milestone_3|Milestone 3 status]]<br />
<br />
=== WebDriver BiDi Milestone 2 - Completed December 19th, 2021 ===<br />
'''Goal''': Extend the current WebDriver BiDi code base to fully support log.entryAdded events and allow clients to unsubscribe from this event.<br />
<br />
'''Details''': [[WebDriver/RemoteProtocol/WebDriver_BiDi/Milestone_2|Milestone 2 status]]<br />
<br />
=== WebDriver BiDi Milestone 1 - Completed September 10th, 2021 ===<br />
'''Goal''': Adapt the existing Remote Agent code base, and make it ready for building support for WebDriver BiDi. Introduce support for basic logging events (plain string message).<br />
<br />
'''Details''': [[WebDriver/RemoteProtocol/WebDriver_BiDi/Milestone_1|Milestone 1 status]]</div>Whimboohttps://wiki.mozilla.org/index.php?title=WebDriver/RemoteProtocol/WebDriver_BiDi/Milestone_8&diff=1246892WebDriver/RemoteProtocol/WebDriver BiDi/Milestone 82023-06-28T12:36:32Z<p>Whimboo: Created page with "= WebDriver BiDi Milestone 8 - In Development = '''Goal''': TODO '''Progress''': * [Tracking dashboard] '''Updates''': * [Weekly Status Updates] '''Queries''': * [ All Bugs..."</p>
<hr />
<div>= WebDriver BiDi Milestone 8 - In Development =<br />
'''Goal''': TODO<br />
<br />
'''Progress''':<br />
* [Tracking dashboard]<br />
<br />
'''Updates''':<br />
* [Weekly Status Updates]<br />
<br />
'''Queries''':<br />
* [ All Bugs]<br />
* [ Available Bugs]<br />
* [ Assigned Bugs]<br />
* [ Completed Bugs]<br />
<br />
'''Milestone Backlog''':<br />
<bugzilla><br />
{<br />
"whiteboard": "[webdriver:m8",<br />
"include_fields":"id, summary, status, assigned_to, cf_fx_points"<br />
}<br />
</bugzilla></div>Whimboohttps://wiki.mozilla.org/index.php?title=WebDriver/RemoteProtocol/WebDriver_BiDi&diff=1246891WebDriver/RemoteProtocol/WebDriver BiDi2023-06-28T12:35:32Z<p>Whimboo: /* Milestones */ Adding milestone 8</p>
<hr />
<div>[https://w3c.github.io/webdriver-bidi WebDriver BiDi] is an extension of the [https://w3c.github.io/webdriver/ WebDriver specification] that offers a bidirectional communication between a webdriver compatible client and a remote end like Firefox. That means that beside sending commands to the browser and receiving responses, it will be also possible to register for certain events (e.g page load, network interception).<br />
<br />
== Product Backlog Status ==<br />
* [https://mzl.la/3crgUad Milestone 8 Candidates (P2)]<br />
* [https://mzl.la/3Rok3pN Future Candidates (P3)]<br />
* [https://mzl.la/3Awn6Wg Full Product Backlog (P2 & P3)]<br />
<br />
== Milestones ==<br />
<br />
=== WebDriver BiDi Milestone 8 - upcoming ===<br />
'''Goal''': TODO<br />
<br />
'''Details''': [[WebDriver/RemoteProtocol/WebDriver_BiDi/Milestone_8|Milestone 8 status]]<br />
<br />
=== WebDriver BiDi Milestone 7 - In Development ===<br />
'''Goal''': This milestone aims to expand the set of APIs supported for creating basic automated tests using WebDriver BiDi. The newly added APIs will include support for HTTP authentication, improved user interaction with pages and prompts. Additionally, efforts will be made to maintain our infrastructure for the existing WebDriver based test suites.<br />
<br />
'''Details''': [[WebDriver/RemoteProtocol/WebDriver_BiDi/Milestone_7|Milestone 7 status]]<br />
<br />
=== WebDriver BiDi Milestone 6 - Completed April 9th, 2023 ===<br />
'''Goal''': Support a minimal set of APIs for creating basic automated tests using WebDriver BiDi.<br />
<br />
'''Details''': [[WebDriver/RemoteProtocol/WebDriver_BiDi/Milestone_6|Milestone 6 status]]<br />
<br />
=== WebDriver BiDi Milestone 5 - Completed January 15th, 2023 ===<br />
'''Goal''': Support required network and page events for HAR file generation.<br />
<br />
'''Details''': [[WebDriver/RemoteProtocol/WebDriver_BiDi/Milestone_5|Milestone 5 status]]<br />
<br />
=== WebDriver BiDi Milestone 4 - Completed September 20th, 2022 ===<br />
'''Goal''': Support evaluating remote scripts, and passing javascript data between the browser and the client and vice-versa.<br />
<br />
'''Details''': [[WebDriver/RemoteProtocol/WebDriver_BiDi/Milestone_4|Milestone 4 status]]<br />
<br />
=== WebDriver BiDi Milestone 3 - Completed May 15th, 2022 ===<br />
'''Goal''': Basic support for the browsingContext.navigate command, and collaboration with the Selenium project to get log.entryAdded support added.<br />
<br />
'''Details''': [[WebDriver/RemoteProtocol/WebDriver_BiDi/Milestone_3|Milestone 3 status]]<br />
<br />
=== WebDriver BiDi Milestone 2 - Completed December 19th, 2021 ===<br />
'''Goal''': Extend the current WebDriver BiDi code base to fully support log.entryAdded events and allow clients to unsubscribe from this event.<br />
<br />
'''Details''': [[WebDriver/RemoteProtocol/WebDriver_BiDi/Milestone_2|Milestone 2 status]]<br />
<br />
=== WebDriver BiDi Milestone 1 - Completed September 10th, 2021 ===<br />
'''Goal''': Adapt the existing Remote Agent code base, and make it ready for building support for WebDriver BiDi. Introduce support for basic logging events (plain string message).<br />
<br />
'''Details''': [[WebDriver/RemoteProtocol/WebDriver_BiDi/Milestone_1|Milestone 1 status]]</div>Whimboohttps://wiki.mozilla.org/index.php?title=WebDriver/RemoteProtocol/WebDriver_BiDi&diff=1245993WebDriver/RemoteProtocol/WebDriver BiDi2023-04-04T08:47:46Z<p>Whimboo: Moved milestone details into sub pages</p>
<hr />
<div>[https://w3c.github.io/webdriver-bidi WebDriver BiDi] is an extension of the [https://w3c.github.io/webdriver/ WebDriver specification] that offers a bidirectional communication between a webdriver compatible client and a remote end like Firefox. That means that beside sending commands to the browser and receiving responses, it will be also possible to register for certain events (e.g page load, network interception).<br />
<br />
== Product Backlog Status ==<br />
* [https://mzl.la/3crgUad Milestone 7 Candidates (P2)]<br />
* [https://mzl.la/3Rok3pN Future Candidates (P3)]<br />
* [https://mzl.la/3Awn6Wg Full Product Backlog (P2 & P3)]<br />
<br />
== Milestones ==<br />
<br />
=== WebDriver BiDi Milestone 7 - Next ===<br />
'''Goal''': This milestone aims to expand the set of APIs supported for creating basic automated tests using WebDriver BiDi. The newly added APIs will include support for HTTP authentication, improved user interaction with pages and prompts. Additionally, efforts will be made to maintain our infrastructure for the existing WebDriver based test suites.<br />
<br />
'''Details''': [[WebDriver/RemoteProtocol/WebDriver_BiDi/Milestone_7|Milestone 7 status]]<br />
<br />
=== WebDriver BiDi Milestone 6 - In Development ===<br />
'''Goal''': Support a minimal set of APIs for creating basic automated tests using WebDriver BiDi.<br />
<br />
'''Details''': [[WebDriver/RemoteProtocol/WebDriver_BiDi/Milestone_6|Milestone 6 status]]<br />
<br />
=== WebDriver BiDi Milestone 5 - Completed January 15th, 2023 ===<br />
'''Goal''': Support required network and page events for HAR file generation.<br />
<br />
'''Details''': [[WebDriver/RemoteProtocol/WebDriver_BiDi/Milestone_5|Milestone 5 status]]<br />
<br />
=== WebDriver BiDi Milestone 4 - Completed September 20th, 2022 ===<br />
'''Goal''': Support evaluating remote scripts, and passing javascript data between the browser and the client and vice-versa.<br />
<br />
'''Details''': [[WebDriver/RemoteProtocol/WebDriver_BiDi/Milestone_4|Milestone 4 status]]<br />
<br />
=== WebDriver BiDi Milestone 3 - Completed May 15th, 2022 ===<br />
'''Goal''': Basic support for the browsingContext.navigate command, and collaboration with the Selenium project to get log.entryAdded support added.<br />
<br />
'''Details''': [[WebDriver/RemoteProtocol/WebDriver_BiDi/Milestone_3|Milestone 3 status]]<br />
<br />
=== WebDriver BiDi Milestone 2 - Completed December 19th, 2021 ===<br />
'''Goal''': Extend the current WebDriver BiDi code base to fully support log.entryAdded events and allow clients to unsubscribe from this event.<br />
<br />
'''Details''': [[WebDriver/RemoteProtocol/WebDriver_BiDi/Milestone_2|Milestone 2 status]]<br />
<br />
=== WebDriver BiDi Milestone 1 - Completed September 10th, 2021 ===<br />
'''Goal''': Adapt the existing Remote Agent code base, and make it ready for building support for WebDriver BiDi. Introduce support for basic logging events (plain string message).<br />
<br />
'''Details''': [[WebDriver/RemoteProtocol/WebDriver_BiDi/Milestone_1|Milestone 1 status]]</div>Whimboohttps://wiki.mozilla.org/index.php?title=WebDriver/RemoteProtocol/WebDriver_BiDi/Milestone_7&diff=1245992WebDriver/RemoteProtocol/WebDriver BiDi/Milestone 72023-04-04T08:46:30Z<p>Whimboo: Created page for milestone 7</p>
<hr />
<div>= WebDriver BiDi Milestone 7 - In Development =<br />
'''Goal''': This milestone aims to expand the set of APIs supported for creating basic automated tests using WebDriver BiDi. The newly added APIs will include support for HTTP authentication, improved user interaction with pages and prompts. Additionally, efforts will be made to maintain our infrastructure for the existing WebDriver based test suites.<br />
<br />
'''Progress''':<br />
* [https://todo Tracking dashboard]<br />
<br />
'''Updates''':<br />
* [https://todo Weekly Status Updates]<br />
<br />
'''Milestone Backlog''':<br />
<bugzilla><br />
{<br />
"whiteboard": "[webdriver:m7",<br />
"priority":["P1"], <br />
"include_fields":"id, summary, status, assigned_to, priority, cf_fx_points"<br />
}<br />
</bugzilla></div>Whimboohttps://wiki.mozilla.org/index.php?title=WebDriver/RemoteProtocol/WebDriver_BiDi/Milestone_1&diff=1245991WebDriver/RemoteProtocol/WebDriver BiDi/Milestone 12023-04-04T08:43:59Z<p>Whimboo: Created page for milestone 1</p>
<hr />
<div>= WebDriver BiDi Milestone 1 - Completed September 10th, 2021 =<br />
'''Goal''': Adapt the existing Remote Agent code base, and make it ready for building support for WebDriver BiDi. Introduce support for basic logging events (plain string message).<br />
<br />
'''Archive''':<br />
* [https://docs.google.com/spreadsheets/d/1eQopdv19kUkyGaNadtNW4Vv5GrFenlSN/edit#gid=1928058659 Tracking dashboard]<br />
* [https://drive.google.com/drive/folders/1szuzMtgknKZi-W6bnP1SIy5HRojn68bU?usp=sharing Weekly Status Updates]<br />
<br />
<bugzilla><br />
{<br />
"whiteboard": "[bidi-m1-mvp]",<br />
"priority":["P1","P2"], <br />
"include_fields":"id, summary, status, assigned_to, priority, cf_fx_points"<br />
}<br />
</bugzilla></div>Whimboohttps://wiki.mozilla.org/index.php?title=WebDriver/RemoteProtocol/WebDriver_BiDi/Milestone_2&diff=1245990WebDriver/RemoteProtocol/WebDriver BiDi/Milestone 22023-04-04T08:43:05Z<p>Whimboo: Created page for milestone 2</p>
<hr />
<div>= WebDriver BiDi Milestone 2 - Completed December 19th, 2021 =<br />
'''Goal''': Extend the current WebDriver BiDi code base to fully support log.entryAdded events and allow clients to unsubscribe from this event.<br />
<br />
'''Archive''':<br />
* [https://docs.google.com/spreadsheets/d/1sUvw3JAstWMUxS8ql09WN1w5Z_zWFUQJ/edit#gid=607278297 Tracking dashboard]<br />
* [https://drive.google.com/drive/folders/1jQtD-ZpHlTjr6DFxwzBjbl8IEFCCricD?usp=sharing Weekly Status Updates]<br />
<br />
<bugzilla><br />
{<br />
"whiteboard": "[bidi-m2-mvp]",<br />
"priority":["P1","P2"], <br />
"include_fields":"id, summary, status, assigned_to, priority, cf_fx_points"<br />
}<br />
</bugzilla></div>Whimboohttps://wiki.mozilla.org/index.php?title=WebDriver/RemoteProtocol/WebDriver_BiDi/Milestone_3&diff=1245989WebDriver/RemoteProtocol/WebDriver BiDi/Milestone 32023-04-04T08:42:23Z<p>Whimboo: Created page for milestone 3</p>
<hr />
<div>= WebDriver BiDi Milestone 3 - Completed May 15th, 2022 =<br />
'''Goal''': Basic support for the browsingContext.navigate command, and collaboration with the Selenium project to get log.entryAdded support added.<br />
<br />
'''Archive''':<br />
* [https://1drv.ms/x/s!AuFRYG6dkmv1zBZJWQCx8bkg6lRa Tracking dashboard]<br />
* [https://drive.google.com/drive/folders/1SvgE7fLC3T0tTgSmchbw6LOieTFbxE6W?usp=sharing Weekly Status Updates]<br />
<br />
<bugzilla><br />
{<br />
"whiteboard": "[bidi-m3-mvp]",<br />
"priority":["P1","P2", "P3"], <br />
"include_fields":"id, summary, status, assigned_to, priority, cf_fx_points"<br />
}<br />
</bugzilla></div>Whimboohttps://wiki.mozilla.org/index.php?title=WebDriver/RemoteProtocol/WebDriver_BiDi/Milestone_4&diff=1245988WebDriver/RemoteProtocol/WebDriver BiDi/Milestone 42023-04-04T08:41:25Z<p>Whimboo: Created page for milestone 4</p>
<hr />
<div>= WebDriver BiDi Milestone 4 - Completed September 20th, 2022 =<br />
'''Goal''': Support evaluating remote scripts, and passing javascript data between the browser and the client and vice-versa.<br />
<br />
'''Archives''':<br />
* [https://1drv.ms/x/s!AuFRYG6dkmv1zzmm1u9wk4tbLkAW?e=yOgc84 Tracking dashboard]<br />
* [https://drive.google.com/drive/folders/17yVQklybsMNs0OZnmXpWUjMDY0knkl0J?usp=sharing Weekly Status Updates]<br />
<br />
'''Milestone Backlog''':<br />
<bugzilla><br />
{<br />
"whiteboard": "[webdriver:m4",<br />
"priority":["P1"], <br />
"include_fields":"id, summary, status, assigned_to, priority, cf_fx_points"<br />
}<br />
</bugzilla></div>Whimboohttps://wiki.mozilla.org/index.php?title=WebDriver/RemoteProtocol/WebDriver_BiDi/Milestone_5&diff=1245987WebDriver/RemoteProtocol/WebDriver BiDi/Milestone 52023-04-04T08:40:18Z<p>Whimboo: Created page for milestone 5</p>
<hr />
<div>= WebDriver BiDi Milestone 5 - Completed January 15th, 2023 =<br />
'''Goal''': Support required network and page events for HAR file generation.<br />
<br />
'''Archives''':<br />
* [https://1drv.ms/x/s!AuFRYG6dkmv15GP6g43vYYbD0y01?e=zVPG2X Tracking dashboard]<br />
* [https://drive.google.com/drive/folders/172VYCRvy8bosJ5lNZwouydpo_1mlLEbB?usp=sharing Weekly Status Updates]<br />
<br />
'''Milestone Backlog''':<br />
<bugzilla><br />
{<br />
"whiteboard": "[webdriver:m5",<br />
"priority":["P1"], <br />
"include_fields":"id, summary, status, assigned_to, priority, cf_fx_points"<br />
}<br />
</bugzilla></div>Whimboohttps://wiki.mozilla.org/index.php?title=WebDriver/RemoteProtocol/WebDriver_BiDi/Milestone_6&diff=1245985WebDriver/RemoteProtocol/WebDriver BiDi/Milestone 62023-04-04T08:37:03Z<p>Whimboo: Whimboo moved page WebDriver/Remote/WebDriver BiDi/Milestone 6 to WebDriver/RemoteProtocol/WebDriver BiDi/Milestone 6 over redirect</p>
<hr />
<div>= WebDriver BiDi Milestone 6 - In Development =<br />
'''Goal''': Support a minimal set of APIs for creating basic automated tests using WebDriver BiDi.<br />
<br />
'''Progress''':<br />
* [https://1drv.ms/x/s!AuFRYG6dkmv150g5Bdy788QhPzqi?e=i7KBQZ Tracking dashboard]<br />
<br />
'''Updates''':<br />
* [https://drive.google.com/drive/folders/1sBMQ-7l-6pp15lkNXJc64xwo4IuoKFaF?usp=sharing Weekly Status Updates]<br />
<br />
'''Queries''':<br />
* [https://mzl.la/3ZFzMWq All Bugs]<br />
* [https://mzl.la/3ZQr1cz Available Bugs]<br />
* [https://mzl.la/3CPyxds Assigned Bugs]<br />
* [https://mzl.la/3IQCNgF Completed Bugs]<br />
<br />
'''Milestone Backlog''':<br />
<bugzilla><br />
{<br />
"whiteboard": "[webdriver:m6",<br />
"priority":["P1"], <br />
"include_fields":"id, summary, status, assigned_to, priority, cf_fx_points"<br />
}<br />
</bugzilla></div>Whimboohttps://wiki.mozilla.org/index.php?title=WebDriver/Remote/WebDriver_BiDi/Milestone_6&diff=1245986WebDriver/Remote/WebDriver BiDi/Milestone 62023-04-04T08:37:03Z<p>Whimboo: Whimboo moved page WebDriver/Remote/WebDriver BiDi/Milestone 6 to WebDriver/RemoteProtocol/WebDriver BiDi/Milestone 6 over redirect</p>
<hr />
<div>#REDIRECT [[WebDriver/RemoteProtocol/WebDriver BiDi/Milestone 6]]</div>Whimboohttps://wiki.mozilla.org/index.php?title=WebDriver/RemoteProtocol/WebDriver_BiDi/Milestone_6&diff=1245983WebDriver/RemoteProtocol/WebDriver BiDi/Milestone 62023-04-04T08:32:56Z<p>Whimboo: Whimboo moved page WebDriver/RemoteProtocol/WebDriver BiDi/Milestone 6 to WebDriver/Remote/WebDriver BiDi/Milestone 6</p>
<hr />
<div>= WebDriver BiDi Milestone 6 - In Development =<br />
'''Goal''': Support a minimal set of APIs for creating basic automated tests using WebDriver BiDi.<br />
<br />
'''Progress''':<br />
* [https://1drv.ms/x/s!AuFRYG6dkmv150g5Bdy788QhPzqi?e=i7KBQZ Tracking dashboard]<br />
<br />
'''Updates''':<br />
* [https://drive.google.com/drive/folders/1sBMQ-7l-6pp15lkNXJc64xwo4IuoKFaF?usp=sharing Weekly Status Updates]<br />
<br />
'''Queries''':<br />
* [https://mzl.la/3ZFzMWq All Bugs]<br />
* [https://mzl.la/3ZQr1cz Available Bugs]<br />
* [https://mzl.la/3CPyxds Assigned Bugs]<br />
* [https://mzl.la/3IQCNgF Completed Bugs]<br />
<br />
'''Milestone Backlog''':<br />
<bugzilla><br />
{<br />
"whiteboard": "[webdriver:m6",<br />
"priority":["P1"], <br />
"include_fields":"id, summary, status, assigned_to, priority, cf_fx_points"<br />
}<br />
</bugzilla></div>Whimboohttps://wiki.mozilla.org/index.php?title=WebDriver/RemoteProtocol/WebDriver_BiDi/Milestone_6&diff=1245982WebDriver/RemoteProtocol/WebDriver BiDi/Milestone 62023-04-04T08:24:42Z<p>Whimboo: Adding page for milestone 6</p>
<hr />
<div>= WebDriver BiDi Milestone 6 - In Development =<br />
'''Goal''': Support a minimal set of APIs for creating basic automated tests using WebDriver BiDi.<br />
<br />
'''Progress''':<br />
* [https://1drv.ms/x/s!AuFRYG6dkmv150g5Bdy788QhPzqi?e=i7KBQZ Tracking dashboard]<br />
<br />
'''Updates''':<br />
* [https://drive.google.com/drive/folders/1sBMQ-7l-6pp15lkNXJc64xwo4IuoKFaF?usp=sharing Weekly Status Updates]<br />
<br />
'''Queries''':<br />
* [https://mzl.la/3ZFzMWq All Bugs]<br />
* [https://mzl.la/3ZQr1cz Available Bugs]<br />
* [https://mzl.la/3CPyxds Assigned Bugs]<br />
* [https://mzl.la/3IQCNgF Completed Bugs]<br />
<br />
'''Milestone Backlog''':<br />
<bugzilla><br />
{<br />
"whiteboard": "[webdriver:m6",<br />
"priority":["P1"], <br />
"include_fields":"id, summary, status, assigned_to, priority, cf_fx_points"<br />
}<br />
</bugzilla></div>Whimboohttps://wiki.mozilla.org/index.php?title=WebDriver&diff=1245634WebDriver2023-02-24T14:09:58Z<p>Whimboo: /* Communication */ Updated Marionette query</p>
<hr />
<div>WebDriver is a remote control interface<br />
that enables introspection and control of user agents.<br />
It provides a platform- and language-neutral wire protocol<br />
as a way for out-of-process programs<br />
to remotely instruct the behavior of web browsers.<br />
<br />
'''This is the project page for the WebDriver project at Mozilla.'''<br />
If you’re looking for [https://developer.mozilla.org/en-US/docs/Web/WebDriver information about WebDriver itself you will find that on MDN].<br />
<br />
== Components ==<br />
The implementation of WebDriver in Firefox consists of different layers with each of them handled by it's own component.<br />
<br />
=== Marionette ===<br />
[[WebDriver/Marionette|Marionette]] is a remote protocol that lets out-of-process programs communicate with, instrument, and control Gecko-based browsers. It implements the [https://w3c.github.io/webdriver/ WebDriver specification], which is then made available via a custom socket protocol to geckodriver.<br />
<br />
It provides interfaces for interacting with both the internal JavaScript runtime and UI elements of Gecko-based browsers, such as Firefox and Fenix. It can control both the content and chrome- documents, giving a high level of control and ability to emulate user interaction.<br />
<br />
=== geckodriver ===<br />
[[WebDriver/geckodriver|geckodriver]] is a proxy for using W3C WebDriver-compatible clients to interact with Gecko-based browsers.<br />
<br />
This program provides the HTTP API described by the [https://w3c.github.io/webdriver/ WebDriver specification] to communicate with Gecko browsers. It translates calls into the [[WebDriver/Marionette|Marionette]] compatible remote protocol by acting as a proxy between the local- and remote ends.<br />
<br />
=== Remote Protocol ===<br />
The Firefox [[WebDriver/RemoteProtocol|Remote Protocol]] is a low-level debugging interface you can use to inspect the state and control execution of documents running in web content, instrument the browser in interesting ways, simulate user interaction for automation purposes, and for subscribing to events in the browser such as network- or console logs.<br />
<br />
It's primary purpose is the implementation of the [https://w3c.github.io/webdriver-bidi/ WebDriver BiDi specification]. But it also complements the existing Firefox Developer Tools [https://firefox-source-docs.mozilla.org/devtools/backend/protocol.html#remote-debugging-protocol Remote Debugging Protocol (RDP)] by implementing a subset of the [https://chromedevtools.github.io/devtools-protocol/ Chrome DevTools Protocol (CDP)].<br />
<br />
==== WebDriver BiDi ====<br />
The WebDriver BiDi specification extends WebDriver HTTP to add bidirectional communication. There is a [[WebDriver/RemoteProtocol/WebDriver_BiDi|WebDriver BiDi project page]] that contains details about the current status and upcoming / planned work.<br />
<br />
== Communication ==<br />
<br />
; Mailing list<br />
: [http://mailto:dev-webdriver@mozilla.org dev-webdriver@mozilla.org] ([https://groups.google.com/a/mozilla.org/g/dev-webdriver subscribe])<br />
; Real-time chat<br />
: The communication channel for the team is [https://chat.mozilla.org/#/room/#webdriver:mozilla.org Element/#webdriver].<br />
; Bug tracking<br />
: [https://bugzilla.mozilla.org/buglist.cgi?product=Remote%20Protocol&component=Marionette&resolution=--- WebDriver (Marionette) in Bugzilla]<br />
: [https://bugzilla.mozilla.org/buglist.cgi?product=Remote%20Protocol&component=WebDriver%20BiDi&resolution=--- WebDriver BiDi in Bugzilla]<br />
: [https://bugzilla.mozilla.org/buglist.cgi?product=Testing&component=geckodriver&resolution=--- geckodriver in Bugzilla]<br />
: [https://github.com/mozilla/geckodriver geckodriver on GitHub]<br />
: [https://bugzilla.mozilla.org/buglist.cgi?product=Testing&component=Mozbase%20Rust&resolution=--- Rust port of mozbase]<br />
<br />
== Staff ==<br />
* Jan Odvarko (honza), manager<br />
* [https://www.hskupin.info/ Henrik Skupin] (whimboo), engineer<br />
* Julian Descottes (jdescottes), engineer<br />
* Alexandra Borovova (sasha), engineer<br />
* [https://hoppipolla.co.uk/ James Graham] (jgraham), engineer (WebDriver Spec)<br />
* Marco Mucci (mmucci), EPM<br />
<br />
== Meetings ==<br />
The team has a public meetings on Mondays at 2:30 pm UTC.<br />
<br />
* See [[WebDriver/Meetings]] for more details and minutes</div>Whimboohttps://wiki.mozilla.org/index.php?title=WebDriver/RemoteProtocol/WebDriver_BiDi&diff=1244001WebDriver/RemoteProtocol/WebDriver BiDi2022-09-21T06:53:44Z<p>Whimboo: Completed milestone 4 and started milestone 5</p>
<hr />
<div>[https://w3c.github.io/webdriver-bidi WebDriver BiDi] is an extension of the [https://w3c.github.io/webdriver/ WebDriver specification] that offers a bidirectional communication between a webdriver compatible client and a remote end like Firefox. That means that beside sending commands to the browser and receiving responses, it will be also possible to register for certain events (e.g page load, network interception).<br />
<br />
== Product Backlog Status ==<br />
* [https://mzl.la/3crgUad Milestone 5 Candidates (P2)]<br />
* [https://mzl.la/3Rok3pN Future Candidates (P3)]<br />
* [https://mzl.la/3Awn6Wg Full Product Backlog (P2 & P3)]<br />
<br />
== Current Milestone Status ==<br />
<br />
=== WebDriver BiDi Milestone 5 - In Development ===<br />
'''Goal''': Support required network and page events for HAR file generation.<br />
<br />
'''Progress''':<br />
* [https:// Tracking dashboard]<br />
<br />
'''Updates''':<br />
* [https://drive.google.com/drive/folders/17yVQklybsMNs0OZnmXpWUjMDY0knkl0J?usp=sharing Weekly Status Updates]<br />
<br />
'''Queries''':<br />
* [https://mzl.la/3qVWABk All Bugs]<br />
* [https://mzl.la/3LtXYEP Available Bugs]<br />
* [https://mzl.la/3qXQ3Gl Assigned Bugs]<br />
* [https://mzl.la/3UpI966 Completed Bugs]<br />
<br />
'''Milestone Backlog''':<br />
<bugzilla><br />
{<br />
"whiteboard": "[webdriver:m5",<br />
"priority":["P1"], <br />
"include_fields":"id, summary, status, assigned_to, priority, cf_fx_points"<br />
}<br />
</bugzilla><br />
<br />
<br />
<br />
<br />
<br />
=== WebDriver BiDi Milestone 4 - Completed September 20th, 2022 ===<br />
'''Goal''': Support evaluating remote scripts, and passing javascript data between the browser and the client and vice-versa.<br />
<br />
'''Progress''':<br />
* [https://1drv.ms/x/s!AuFRYG6dkmv1zzmm1u9wk4tbLkAW?e=yOgc84 Tracking dashboard]<br />
<br />
'''Updates''':<br />
* [https://drive.google.com/drive/folders/17yVQklybsMNs0OZnmXpWUjMDY0knkl0J?usp=sharing Weekly Status Updates]<br />
<br />
'''Queries''':<br />
* [https://mzl.la/3JH1gDB All Bugs]<br />
* [https://mzl.la/3Q8O1Oy Available Bugs]<br />
* [https://mzl.la/3NsMjWn Assigned Bugs]<br />
* [https://mzl.la/3LD714s Completed Bugs]<br />
<br />
'''Milestone Backlog''':<br />
<bugzilla><br />
{<br />
"whiteboard": "[webdriver:m4",<br />
"priority":["P1"], <br />
"include_fields":"id, summary, status, assigned_to, priority, cf_fx_points"<br />
}<br />
</bugzilla><br />
<br />
=== WebDriver BiDi Milestone 3 - Completed May 15th, 2022 ===<br />
'''Goal''': Basic support for the browsingContext.navigate command, and collaboration with the Selenium project to get log.entryAdded support added.<br />
<br />
<bugzilla><br />
{<br />
"whiteboard": "[bidi-m3-mvp]",<br />
"priority":["P1","P2", "P3"], <br />
"include_fields":"id, summary, status, assigned_to, priority, cf_fx_points"<br />
}<br />
</bugzilla><br />
<br />
=== WebDriver BiDi Milestone 2 - Completed December 19th, 2021 ===<br />
'''Goal''': Extend the current WebDriver BiDi code base to fully support log.entryAdded events and allow clients to unsubscribe from this event.<br />
<br />
<bugzilla><br />
{<br />
"whiteboard": "[bidi-m2-mvp]",<br />
"priority":["P1","P2"], <br />
"include_fields":"id, summary, status, assigned_to, priority, cf_fx_points"<br />
}<br />
</bugzilla><br />
<br />
=== WebDriver BiDi Milestone 1 - Completed September 10th, 2021 ===<br />
'''Goal''': Adapt the existing Remote Agent code base, and make it ready for building support for WebDriver BiDi. Introduce support for basic logging events (plain string message).<br />
<br />
<bugzilla><br />
{<br />
"whiteboard": "[bidi-m1-mvp]",<br />
"priority":["P1","P2"], <br />
"include_fields":"id, summary, status, assigned_to, priority, cf_fx_points"<br />
}<br />
</bugzilla></div>Whimboohttps://wiki.mozilla.org/index.php?title=WebDriver/RemoteProtocol/WebDriver_BiDi&diff=1242633WebDriver/RemoteProtocol/WebDriver BiDi2022-05-25T11:31:08Z<p>Whimboo: Marked milestone 3 as completed</p>
<hr />
<div>[https://w3c.github.io/webdriver-bidi WebDriver BiDi] is an extension of the [https://w3c.github.io/webdriver/ WebDriver specification] that offers a bidirectional communication between a webdriver compatible client and a remote end like Firefox. That means that beside sending commands to the browser and receiving responses, it will be also possible to register for certain events (e.g page load, network interception).<br />
<br />
== Project Status ==<br />
=== WebDriver BiDi Milestone 4 ===<br />
'''Goal''': Support evaluating remote scripts, and passing javascript data between the browser and the client and vice-versa.<br />
<br />
'''Progress''':<br />
* Tracking dashboard - ''To Be Developed''<br />
<br />
'''Updates''':<br />
* Weekly Status Updates - ''To Be Developed''<br />
<br />
'''Queries''':<br />
* [https://mzl.la/3lDjKcQ All Bugs]<br />
* [https://mzl.la/3G6jlt8 Available Bugs]<br />
* [https://mzl.la/3NsMjWn Assigned Bugs]<br />
* [https://mzl.la/3LD714s Completed Bugs]<br />
<br />
'''Milestone Backlog''':<br />
<bugzilla><br />
{<br />
"whiteboard": "[webdriver:m4]",<br />
"priority":["P1"], <br />
"include_fields":"id, summary, status, assigned_to, priority, cf_fx_points"<br />
}<br />
</bugzilla><br />
<br />
=== WebDriver BiDi Milestone 3 (completed - May 15th, 2022) ===<br />
'''Goal''': Basic support for the browsingContext.navigate command, and collaboration with the Selenium project to get log.entryAdded support added.<br />
<br />
'''Progress''': [https://onedrive.live.com/view.aspx?resid=F56B929D6E6051E1!9750&ithint=file%2cxlsx&authkey=!AElZALHxuSDqVFo Tracking dashboard]<br />
<br />
<bugzilla><br />
{<br />
"whiteboard": "[bidi-m3-mvp]",<br />
"priority":["P1","P2", "P3"], <br />
"include_fields":"id, summary, status, assigned_to, priority, cf_fx_points"<br />
}<br />
</bugzilla><br />
<br />
=== WebDriver BiDi Milestone 2 (completed - December 19th, 2021) ===<br />
'''Goal''': Extend the current WebDriver BiDi code base to fully support log.entryAdded events and allow clients to unsubscribe from this event.<br />
<br />
<bugzilla><br />
{<br />
"whiteboard": "[bidi-m2-mvp]",<br />
"priority":["P1","P2"], <br />
"include_fields":"id, summary, status, assigned_to, priority, cf_fx_points"<br />
}<br />
</bugzilla><br />
<br />
=== WebDriver BiDi Milestone 1 (completed - September 10th, 2021) ===<br />
'''Goal''': Adapt the existing Remote Agent code base, and make it ready for building support for WebDriver BiDi. Introduce support for basic logging events (plain string message).<br />
<br />
This milestone has been completed on September 10th, 2021.<br />
<br />
<bugzilla><br />
{<br />
"whiteboard": "[bidi-m1-mvp]",<br />
"priority":["P1","P2"], <br />
"include_fields":"id, summary, status, assigned_to, priority, cf_fx_points"<br />
}<br />
</bugzilla></div>Whimboohttps://wiki.mozilla.org/index.php?title=WebDriver&diff=1242500WebDriver2022-05-19T16:46:11Z<p>Whimboo: /* Staff */ Fix spelling mistake</p>
<hr />
<div>WebDriver is a remote control interface<br />
that enables introspection and control of user agents.<br />
It provides a platform- and language-neutral wire protocol<br />
as a way for out-of-process programs<br />
to remotely instruct the behavior of web browsers.<br />
<br />
'''This is the project page for the WebDriver project at Mozilla.'''<br />
If you’re looking for [https://developer.mozilla.org/en-US/docs/Web/WebDriver information about WebDriver itself you will find that on MDN].<br />
<br />
== Components ==<br />
The implementation of WebDriver in Firefox consists of different layers with each of them handled by it's own component.<br />
<br />
=== Marionette ===<br />
[[WebDriver/Marionette|Marionette]] is a remote protocol that lets out-of-process programs communicate with, instrument, and control Gecko-based browsers. It implements the [https://w3c.github.io/webdriver/ WebDriver specification], which is then made available via a custom socket protocol to geckodriver.<br />
<br />
It provides interfaces for interacting with both the internal JavaScript runtime and UI elements of Gecko-based browsers, such as Firefox and Fenix. It can control both the content and chrome- documents, giving a high level of control and ability to emulate user interaction.<br />
<br />
=== geckodriver ===<br />
[[WebDriver/geckodriver|geckodriver]] is a proxy for using W3C WebDriver-compatible clients to interact with Gecko-based browsers.<br />
<br />
This program provides the HTTP API described by the [https://w3c.github.io/webdriver/ WebDriver specification] to communicate with Gecko browsers. It translates calls into the [[WebDriver/Marionette|Marionette]] compatible remote protocol by acting as a proxy between the local- and remote ends.<br />
<br />
=== Remote Protocol ===<br />
The Firefox [[WebDriver/RemoteProtocol|Remote Protocol]] is a low-level debugging interface you can use to inspect the state and control execution of documents running in web content, instrument the browser in interesting ways, simulate user interaction for automation purposes, and for subscribing to events in the browser such as network- or console logs.<br />
<br />
It's primary purpose is the implementation of the [https://w3c.github.io/webdriver-bidi/ WebDriver BiDi specification]. But it also complements the existing Firefox Developer Tools [https://firefox-source-docs.mozilla.org/devtools/backend/protocol.html#remote-debugging-protocol Remote Debugging Protocol (RDP)] by implementing a subset of the [https://chromedevtools.github.io/devtools-protocol/ Chrome DevTools Protocol (CDP)].<br />
<br />
==== WebDriver BiDi ====<br />
The WebDriver BiDi specification extends WebDriver HTTP to add bidirectional communication. There is a [[WebDriver/RemoteProtocol/WebDriver_BiDi|WebDriver BiDi project page]] that contains details about the current status and upcoming / planned work.<br />
<br />
== Communication ==<br />
<br />
; Mailing list<br />
: [http://mailto:dev-webdriver@mozilla.org dev-webdriver@mozilla.org] ([https://groups.google.com/a/mozilla.org/g/dev-webdriver subscribe])<br />
; Real-time chat<br />
: The communication channel for the team is [https://chat.mozilla.org/#/room/#webdriver:mozilla.org Element/#webdriver].<br />
; Bug tracking<br />
: [https://bugzilla.mozilla.org/buglist.cgi?product=Testing&component=Marionette&resolution=--- WebDriver (Marionette) in Bugzilla]<br />
: [https://bugzilla.mozilla.org/buglist.cgi?product=Remote%20Protocol&component=WebDriver%20BiDi&resolution=--- WebDriver BiDi in Bugzilla]<br />
: [https://bugzilla.mozilla.org/buglist.cgi?product=Testing&component=geckodriver&resolution=--- geckodriver in Bugzilla]<br />
: [https://github.com/mozilla/geckodriver geckodriver on GitHub]<br />
: [https://bugzilla.mozilla.org/buglist.cgi?product=Testing&component=Mozbase%20Rust&resolution=--- Rust port of mozbase]<br />
<br />
== Staff ==<br />
* Jan Odvarko (honza), manager<br />
* [https://www.hskupin.info/ Henrik Skupin] (whimboo), engineer<br />
* Julian Descottes (jdescottes), engineer<br />
* Alexandra Borovova (sasha), engineer<br />
* [https://hoppipolla.co.uk/ James Graham] (jgraham), engineer (WebDriver Spec)<br />
* Marco Mucci (mmucci), EPM<br />
<br />
== Meetings ==<br />
The team has a public meetings on Mondays at 2:30 pm UTC.<br />
<br />
* See [[WebDriver/Meetings]] for more details and minutes</div>Whimboohttps://wiki.mozilla.org/index.php?title=WebDriver&diff=1242499WebDriver2022-05-19T15:52:27Z<p>Whimboo: Linked the WebDriver BiDi project page</p>
<hr />
<div>WebDriver is a remote control interface<br />
that enables introspection and control of user agents.<br />
It provides a platform- and language-neutral wire protocol<br />
as a way for out-of-process programs<br />
to remotely instruct the behavior of web browsers.<br />
<br />
'''This is the project page for the WebDriver project at Mozilla.'''<br />
If you’re looking for [https://developer.mozilla.org/en-US/docs/Web/WebDriver information about WebDriver itself you will find that on MDN].<br />
<br />
== Components ==<br />
The implementation of WebDriver in Firefox consists of different layers with each of them handled by it's own component.<br />
<br />
=== Marionette ===<br />
[[WebDriver/Marionette|Marionette]] is a remote protocol that lets out-of-process programs communicate with, instrument, and control Gecko-based browsers. It implements the [https://w3c.github.io/webdriver/ WebDriver specification], which is then made available via a custom socket protocol to geckodriver.<br />
<br />
It provides interfaces for interacting with both the internal JavaScript runtime and UI elements of Gecko-based browsers, such as Firefox and Fenix. It can control both the content and chrome- documents, giving a high level of control and ability to emulate user interaction.<br />
<br />
=== geckodriver ===<br />
[[WebDriver/geckodriver|geckodriver]] is a proxy for using W3C WebDriver-compatible clients to interact with Gecko-based browsers.<br />
<br />
This program provides the HTTP API described by the [https://w3c.github.io/webdriver/ WebDriver specification] to communicate with Gecko browsers. It translates calls into the [[WebDriver/Marionette|Marionette]] compatible remote protocol by acting as a proxy between the local- and remote ends.<br />
<br />
=== Remote Protocol ===<br />
The Firefox [[WebDriver/RemoteProtocol|Remote Protocol]] is a low-level debugging interface you can use to inspect the state and control execution of documents running in web content, instrument the browser in interesting ways, simulate user interaction for automation purposes, and for subscribing to events in the browser such as network- or console logs.<br />
<br />
It's primary purpose is the implementation of the [https://w3c.github.io/webdriver-bidi/ WebDriver BiDi specification]. But it also complements the existing Firefox Developer Tools [https://firefox-source-docs.mozilla.org/devtools/backend/protocol.html#remote-debugging-protocol Remote Debugging Protocol (RDP)] by implementing a subset of the [https://chromedevtools.github.io/devtools-protocol/ Chrome DevTools Protocol (CDP)].<br />
<br />
==== WebDriver BiDi ====<br />
The WebDriver BiDi specification extends WebDriver HTTP to add bidirectional communication. There is a [[WebDriver/RemoteProtocol/WebDriver_BiDi|WebDriver BiDi project page]] that contains details about the current status and upcoming / planned work.<br />
<br />
== Communication ==<br />
<br />
; Mailing list<br />
: [http://mailto:dev-webdriver@mozilla.org dev-webdriver@mozilla.org] ([https://groups.google.com/a/mozilla.org/g/dev-webdriver subscribe])<br />
; Real-time chat<br />
: The communication channel for the team is [https://chat.mozilla.org/#/room/#webdriver:mozilla.org Element/#webdriver].<br />
; Bug tracking<br />
: [https://bugzilla.mozilla.org/buglist.cgi?product=Testing&component=Marionette&resolution=--- WebDriver (Marionette) in Bugzilla]<br />
: [https://bugzilla.mozilla.org/buglist.cgi?product=Remote%20Protocol&component=WebDriver%20BiDi&resolution=--- WebDriver BiDi in Bugzilla]<br />
: [https://bugzilla.mozilla.org/buglist.cgi?product=Testing&component=geckodriver&resolution=--- geckodriver in Bugzilla]<br />
: [https://github.com/mozilla/geckodriver geckodriver on GitHub]<br />
: [https://bugzilla.mozilla.org/buglist.cgi?product=Testing&component=Mozbase%20Rust&resolution=--- Rust port of mozbase]<br />
<br />
== Staff ==<br />
* Jan Odvarko (honza), manager<br />
* [https://www.hskupin.info/ Henrik Skupin] (whimboo), engineer<br />
* Julian Descottes (jdescottes), engineer<br />
* Alexandra Bororova (sasha), engineer<br />
* [https://hoppipolla.co.uk/ James Graham] (jgraham), engineer (WebDriver Spec)<br />
* Marco Mucci (mmucci), EPM<br />
<br />
== Meetings ==<br />
The team has a public meetings on Mondays at 2:30 pm UTC.<br />
<br />
* See [[WebDriver/Meetings]] for more details and minutes</div>Whimboohttps://wiki.mozilla.org/index.php?title=WebDriver&diff=1242498WebDriver2022-05-19T15:45:04Z<p>Whimboo: /* Staff */ Adding Sasha</p>
<hr />
<div>WebDriver is a remote control interface<br />
that enables introspection and control of user agents.<br />
It provides a platform- and language-neutral wire protocol<br />
as a way for out-of-process programs<br />
to remotely instruct the behavior of web browsers.<br />
<br />
'''This is the project page for the WebDriver project at Mozilla.'''<br />
If you’re looking for [https://developer.mozilla.org/en-US/docs/Web/WebDriver information about WebDriver itself you will find that on MDN].<br />
<br />
== Components ==<br />
The implementation of WebDriver in Firefox consists of different layers with each of them handled by it's own component.<br />
<br />
=== Marionette ===<br />
[[WebDriver/Marionette|Marionette]] is a remote protocol that lets out-of-process programs communicate with, instrument, and control Gecko-based browsers. It implements the [https://w3c.github.io/webdriver/ WebDriver specification], which is then made available via a custom socket protocol to geckodriver.<br />
<br />
It provides interfaces for interacting with both the internal JavaScript runtime and UI elements of Gecko-based browsers, such as Firefox and Fenix. It can control both the content and chrome- documents, giving a high level of control and ability to emulate user interaction.<br />
<br />
=== geckodriver ===<br />
[[WebDriver/geckodriver|geckodriver]] is a proxy for using W3C WebDriver-compatible clients to interact with Gecko-based browsers.<br />
<br />
This program provides the HTTP API described by the [https://w3c.github.io/webdriver/ WebDriver specification] to communicate with Gecko browsers. It translates calls into the [[WebDriver/Marionette|Marionette]] compatible remote protocol by acting as a proxy between the local- and remote ends.<br />
<br />
=== Remote Protocol ===<br />
The Firefox [[WebDriver/RemoteProtocol|Remote Protocol]] is a low-level debugging interface you can use to inspect the state and control execution of documents running in web content, instrument the browser in interesting ways, simulate user interaction for automation purposes, and for subscribing to events in the browser such as network- or console logs.<br />
<br />
It's primary purpose is the implementation of the [https://w3c.github.io/webdriver-bidi/ WebDriver BiDi specification]. But it also complements the existing Firefox Developer Tools [https://firefox-source-docs.mozilla.org/devtools/backend/protocol.html#remote-debugging-protocol Remote Debugging Protocol (RDP)] by implementing a subset of the [https://chromedevtools.github.io/devtools-protocol/ Chrome DevTools Protocol (CDP)].<br />
<br />
== Communication ==<br />
<br />
; Mailing list<br />
: [http://mailto:dev-webdriver@mozilla.org dev-webdriver@mozilla.org] ([https://groups.google.com/a/mozilla.org/g/dev-webdriver subscribe])<br />
; Real-time chat<br />
: The communication channel for the team is [https://chat.mozilla.org/#/room/#webdriver:mozilla.org Element/#webdriver].<br />
; Bug tracking<br />
: [https://bugzilla.mozilla.org/buglist.cgi?product=Testing&component=Marionette&resolution=--- WebDriver (Marionette) in Bugzilla]<br />
: [https://bugzilla.mozilla.org/buglist.cgi?product=Remote%20Protocol&component=WebDriver%20BiDi&resolution=--- WebDriver BiDi in Bugzilla]<br />
: [https://bugzilla.mozilla.org/buglist.cgi?product=Testing&component=geckodriver&resolution=--- geckodriver in Bugzilla]<br />
: [https://github.com/mozilla/geckodriver geckodriver on GitHub]<br />
: [https://bugzilla.mozilla.org/buglist.cgi?product=Testing&component=Mozbase%20Rust&resolution=--- Rust port of mozbase]<br />
<br />
== Staff ==<br />
* Jan Odvarko (honza), manager<br />
* [https://www.hskupin.info/ Henrik Skupin] (whimboo), engineer<br />
* Julian Descottes (jdescottes), engineer<br />
* Alexandra Bororova (sasha), engineer<br />
* [https://hoppipolla.co.uk/ James Graham] (jgraham), engineer (WebDriver Spec)<br />
* Marco Mucci (mmucci), EPM<br />
<br />
== Meetings ==<br />
The team has a public meetings on Mondays at 2:30 pm UTC.<br />
<br />
* See [[WebDriver/Meetings]] for more details and minutes</div>Whimboohttps://wiki.mozilla.org/index.php?title=Platform/Integration/InjectEject/Launcher_Process/&diff=1242289Platform/Integration/InjectEject/Launcher Process/2022-05-10T08:50:25Z<p>Whimboo: /* Starting Firefox via Automation / Scripting */ It also applies for the `remote-debugging-port` command line argument</p>
<hr />
<div>== Introduction ==<br />
In Windows builds of Firefox, the Launcher Process is the initial process that is started when the user runs Firefox. Its sole purpose is to create the browser process in a suspended state, configure the browser process, resume the browser process, and then hand off GUI foreground to the browser. Once the launcher process has completed this objective, it exits.<br />
<br />
The configuration actions performed by the launcher process provide security, performance, and stability enhancements that improve the Firefox user experience:<br />
<br />
* The launcher process creates the browser process with various process mitigation policies, dependent on the underlying version of Windows.<br />
* If the launcher process was started by a user running with full Administrator privileges (ie. at a high integrity level), it configures the browser to run as a normal user.<br />
* The launcher process performs early initialization of the DLL blocklist.<br />
<br />
Since the launcher process is part of the critical path of Firefox startup, special considerations need to be taken when working on its code:<br />
* Its code must be as fast and efficient as possible;<br />
* It must recover gracefully from failures;<br />
* Its code must be self-contained inside <code>firefox.exe</code>;<br />
* Its code cannot start nor rely on prefs, XPCOM, <code>nsString</code>, crash reporter, or other aspects of the Gecko runtime. Header-only code that does not depend on <code>xul.dll</code> (such as MFBT) is safe to use in the launcher process;<br />
* Some parts of its code must be freestanding -- that is, those parts cannot assume the presence of either the C runtime or the Win32 API.<br />
<br />
== Considerations for Users ==<br />
=== Dropping Full Administrator Privileges ===<br />
The Launcher Process selects one of multiple techniques for dropping the privileges of the browser process:<br />
* When UAC is enabled, the launcher process requests that Explorer starts the browser. This ensures that the browser runs under the privileges of the user whose desktop we are currently running in. As an example of a scenario where this might be useful, suppose that a user is starting Firefox from within their command prompt, but they accidentally used their elevated command prompt instead of their normal command prompt.<br />
* When UAC is disabled, the launcher process duplicates the user's token and drops the duplicate token's integrity level from high to medium. The launcher process then creates the browser process using that medium-integrity token.<br />
** Firefox will not have write access to directories that are configured with a high-integrity ACL. By default, this includes root directories, <code>\Program Files</code>, <code>\windows\system32</code>, among others.<br />
** Firefox will be affected by User Interface Privilege Isolation (UIPI); the Firefox UI is not allowed to communicate with other UI running at higher integrity levels. Since the user's desktop and other applications are most likely still running at high integrity level, the Firefox UI will not be able to communicate with them. This means that certain GUI features such as drag-and-drop will not work.<br />
** We have an [https://support.mozilla.org/en-US/kb/windows-administrator-launcher-process-error-fix article in the SUMO Knowledge Base] instructing users on how to mitigate these issues.<br />
*** Note: '''Do not''' advise users to attempt these suggestions unless it is known for a fact that they are running as Administrator with UAC disabled! It is not a "catch-all" solution for launcher process problems.<br />
<br />
=== Starting Firefox via Automation / Scripting ===<br />
As mentioned in the introduction, once the launcher process has handed GUI foreground off to the browser process, the launcher process exits. For users who are starting Firefox via a batch file or script, this may present a problem if the script is written to assume that Firefox has closed before continuing to execute.<br />
<br />
The solution to this is to modify the script by adding the <code>-wait-for-browser</code> option to the Firefox command line.<br />
<br />
The launcher process also implicitly waits for the browser under any combination of the following conditions:<br />
* Firefox is started with the <code>-marionette</code> command line option;<br />
* Firefox is started with the <code>-headless</code> command line option;<br />
* Firefox is started with the <code>-remote-debugging-port</code> command line option;<br />
* Firefox is started with the <code>MOZ_AUTOMATION</code> environment variable set;<br />
* Firefox is started with the <code>MOZ_HEADLESS</code> environment variable set;<br />
<br />
'''''Why does the Launcher Process not wait for the browser by default?'''''<br />
<br />
* Over the course of a Firefox browsing session, the launcher process would lie dormant and its private virtual memory would eventually be paged out to disk. However, it would still be visible as yet another <code>firefox.exe</code> process in the operating system's process list.<br />
** To avoid the launcher process being charged against Firefox's overall resource usage (and the public perceptions that doing so would entail), we let the launcher process exit.<br />
** We also do not want launcher process VM to be unnecessarily occupying space in the page file on machines where there is limited page file space. This is not uncommon - see our various OOM crash reports if you don't believe it!<br />
* This would not work with the scenario where an elevated launcher process asks Explorer to restart the browser as a normal user; Explorer does not return any process ID or handle information to the launcher process, so there is nothing for the launcher process to wait on. This would introduce an undesirable inconsistency in the command-line behavior of the launcher process. By explicitly opting into waiting for the browser process, the launcher process adjusts its behavior to avoid this scenario, but uses a less desirable mechanism for restarting the browser.<br />
<br />
== Considerations for Developers ==<br />
* The launcher process is enabled by default both in local and CI builds. In local builds, the launcher process may be disabled by default by specifying the <code>--disable-launcher-process</code> option in <code>mozconfig</code>. Leaving this as its default is preferred to ensure that the launcher process receives just as much testing as our other processes.<br />
** If you have disabled the launcher process by default in your local build, but would like to run it during a test, use the <code>-launcher</code> command-line option.<br />
* Both <code>mach run</code> and <code>mach gtest</code> automatically specify the <code>-wait-for-browser</code> option when starting Firefox. Visual Studio projects generated by the build system also automatically include this flag when running Firefox.<br />
* Developers using the Visual Studio Debugger should install the [https://devblogs.microsoft.com/devops/introducing-the-child-process-debugging-power-tool/ Child Process Debugging Power Tool] to enable the debugger to attach to multiple processes simultaneously.<br />
* WinDbg users should either open Firefox with the <code>Debug child processes also</code> option checked, or if starting from the command line, including the <code>-o</code> option.<br />
<br />
The Launcher Process also supports the following environment variables for debugging:<br />
* Setting <code>MOZ_DEBUG_BROWSER_PROCESS</code> causes the browser process to trigger a breakpoint during initial startup;<br />
* Setting <code>MOZ_DEBUG_BROWSER_PAUSE</code> to a positive integer causes the browser process to print its process ID to <code>stderr</code> and pause for <code>MOZ_DEBUG_BROWSER_PAUSE</code> seconds before resuming, thus offering the developer a chance to attach a debugger.<br />
<br />
As previously mentioned, the launcher process is designed to be resilient against failures. If the launcher process encounters an error, it automatically disables itself for future instantiations of Firefox. On the other hand, developers may want to intentionally reproduce those failures. To forcibly run the launcher process despite being previously disabled, specify the <code>-force-launcher</code> option on the command line.<br />
<br />
== Other Troubleshooting ==<br />
If the launcher process fails and telemetry is enabled, the launcher process generates and sends [https://firefox-source-docs.mozilla.org/toolkit/components/telemetry/data/launcher-process-failure-ping.html a telemetry ping] containing an error code and the source code location of the failure. If telemetry is disabled, or if for some reason the launcher process was unable to successfully send its telemetry ping, the launcher process will log the failure to the Windows event log.<br />
<br />
The submitted telemetry is available in [https://iodide.telemetry.mozilla.org/notebooks/219/?viewMode=report this dashboard]. It's important to keep the failure numbers low.<br />
<br />
To view launcher process failure events in the system event viewer, open the <code>Control Panel</code> [''Note: this must be the legacy <code>Control Panel</code> app, not the new <code>Settings</code> app found in Windows 8 and Windows 10''], select <code>Administrative Tools</code>, and double-click on <code>Event Viewer</code>. Looking at the tree in the left pane, expand the <code>Windows Logs</code> branch, and click <code>Application</code>.<br />
<br />
It is also possible to force the launcher process to always log failures to the Windows event log by adding the <code>-log-launcher-error</code> option to the command line. This may be useful when assisting specific users who are experiencing launcher process failures.</div>Whimboohttps://wiki.mozilla.org/index.php?title=WebDriver/RemoteProtocol/WebDriver_BiDi&diff=1241206WebDriver/RemoteProtocol/WebDriver BiDi2022-03-14T15:16:53Z<p>Whimboo: /* WebDriver BiDi Milestone 3 (required) */ Added link to M3 progress</p>
<hr />
<div>[https://w3c.github.io/webdriver-bidi WebDriver BiDi] is an extension of the [https://w3c.github.io/webdriver/ WebDriver specification] that offers a bidirectional communication between a webdriver compatible client and a remote end like Firefox. That means that beside sending commands to the browser and receiving responses, it will be also possible to register for certain events (e.g page load, network interception).<br />
<br />
== Project Status ==<br />
=== WebDriver BiDi Milestone 3 (required) ===<br />
'''Goal''': Basic support for the browsingContext.navigate command, and collaboration with the Selenium project to get log.entryAdded support added.<br />
<br />
'''Progress''': [https://onedrive.live.com/view.aspx?resid=F56B929D6E6051E1!9750&ithint=file%2cxlsx&authkey=!AElZALHxuSDqVFo Tracking dashboard]<br />
<br />
<br />
<bugzilla><br />
{<br />
"whiteboard": "[bidi-m3-mvp]",<br />
"priority":["P1","P2"], <br />
"include_fields":"id, summary, status, assigned_to, priority, cf_fx_points"<br />
}<br />
</bugzilla><br />
<br />
=== WebDriver BiDi Milestone 3 (reserved) ===<br />
<bugzilla><br />
{<br />
"whiteboard": "[bidi-m3-mvp]", <br />
"priority":["P3"], <br />
"include_fields":"id, summary, status, assigned_to, priority, cf_fx_points"<br />
}<br />
</bugzilla><br />
<br />
=== WebDriver BiDi Milestone 2 (completed - 12/19/21) ===<br />
'''Goal''': Extend the current WebDriver BiDi code base to fully support log.entryAdded events and allow clients to unsubscribe from this event.<br />
<br />
<bugzilla><br />
{<br />
"whiteboard": "[bidi-m2-mvp]",<br />
"priority":["P1","P2"], <br />
"include_fields":"id, summary, status, assigned_to, priority, cf_fx_points"<br />
}<br />
</bugzilla><br />
<br />
=== WebDriver BiDi Milestone 1 (completed - 09/10/21) ===<br />
'''Goal''': Adapt the existing Remote Agent code base, and make it ready for building support for WebDriver BiDi. Introduce support for basic logging events (plain string message).<br />
<br />
This milestone has been completed on September 10th, 2021.<br />
<br />
<bugzilla><br />
{<br />
"whiteboard": "[bidi-m1-mvp]",<br />
"priority":["P1","P2"], <br />
"include_fields":"id, summary, status, assigned_to, priority, cf_fx_points"<br />
}<br />
</bugzilla></div>Whimboohttps://wiki.mozilla.org/index.php?title=Modules/Other&diff=1240194Modules/Other2022-01-24T09:52:16Z<p>Whimboo: Move Maja Frydrychowicz to peer emeritus and add Julian Descottes as peer</p>
<hr />
<div><noinclude><br />
'''Only module owners may edit this page.''' <br />
<br />
They may:<br />
<br />
* update any information about their module except the name of the owner<br />
* add or remove sub-modules<br />
* change the owner of a sub-module <br />
* add emeritus owners or peers<br />
<br />
Other changes, including changes of module owner or addition/removal of modules, must be agreed with the Module Ownership Module group, probably via a discussion in [https://www.mozilla.org/about/forums/#governance mozilla.governance].<br />
</noinclude><br />
<br />
{{Module<br />
|name=Content Services Infrastructure<br />
|description=A set of data services that allow for content to be served and measured<br />
|owner=[mailto:nanjiang@mozilla.com Nan Jiang]<br />
|peers=[mailto:tspurway@mozilla.com Tim Spurway]<br />
|peersemeritus=[mailto:dougt@mozilla.org Doug Turner], [mailto:olivier@olivieryiptong.com Olivier Yiptong]<br />
|source_dirs=https://github.com/mozilla/onyx, https://github.com/mozilla/splice, https://github.com/mozilla/infernyx, https://github.com/mozilla/learnyx<br />
|url=https://wiki.mozilla.org/Tiles<br />
|components=Content Services<br />
}}<br />
<br />
{{Module<br />
|name=DevTools<br />
|description=Mozilla Developer Tools<br />
|owner=[mailto:honza@mozilla.com Jan 'Honza' Odvarko]<br />
|peers=[mailto:apoirot@mozilla.com Alex Poirot], [mailto:jdescottes@mozilla.com Julian Descottes], [mailto:nchevobbe@mozilla.com Nicolas Chevobbe], [mailto:balbeza@mozilla.com Belén Albeza], [mailto:bomsy@mozilla.com Hubert Manilla], [mailto:hskupin@mozilla.com Henrik Skupin]<br />
|ownersemeritus=Patrick Brosset, Joe Walker, Dave Camp, Rob Campbell<br />
|peersemeritus=Mihai Șucan, Heather Arthur, Anton Kovalyov, Brandon Benvie, Eddy Bruel, James Long, Matteo Ferretti, Steve Fink (heapsnapshot code), Jaroslav Šnajdr, Tom Tromey, Paul Rouget, Victor Porof, Lin Clark, Jan Keromnes, Jordan Santell, Soledad Penadés, Mike Ratcliffe, Panagiotis Astithas, [mailto:ntim.bugs@gmail.com Tim Nguyen], [mailto:bgrinstead@mozilla.com Brian Grinstead], [mailto:jryans@gmail.com J. Ryan Stinnett], Jason Laster, David Walsh, [mailto:gtatum@mozilla.com Greg Tatum], [mailto:gl@mozilla.com Gabriel Luong], [mailto:bwerth@mozilla.com Brad Werth], [mailto:dakatsuka.birchill@mozilla.com Daisuke Akatsuka], [mailto:ystartsev@mozilla.com Yulia Startsev], [mailto:logan.f.smyth@gmail.com Logan Smyth], [mailto:jwajsberg@mozilla.com Julien Wajsberg], Razvan Caliman, [mailto:mtigley@mozilla.com Micah Tigley], Nick Fitzgerald, [mailto:jblandy@mozilla.com Jim Blandy]<br />
|group=dev-developer-tools<br />
|source_dirs=devtools<br />
|url=https://wiki.mozilla.org/DevTools, http://firefox-dev.tools/<br />
|components=DevTools<br />
}}<br />
<br />
{{Module<br />
|name=Firefox for iOS (Fennec)<br />
|description=Mobile Web Browser<br />
|owner=[mailto:sarentz@mozilla.com Stefan Arentz]<br />
|peers=[mailto:fpatel@mozilla.com Farhan Patel] [mailto:jdarcangelo@mozilla.com Justin D'Arcangelo], [mailto:etoop@mozilla.com Emily Toop], [mailto:jhugman@mozilla.com James Hugman]<br />
|group=https://mail.mozilla.org/listinfo/mobile-firefox-dev<br />
|source_dirs=https://github.com/mozilla/firefox-ios<br />
|url=https://wiki.mozilla.org/Fennec<br />
|components=Firefox for iOS<br />
}}<br />
<br />
{{Module<br />
|name=Firefox Accounts<br />
|description=The Firefox Accounts identity provider and the integration of user-data services tied to a Firefox Account. Where this work overlaps with existing modules (e.g. FX front-end, FX Android front-end, FXOS), design and code reviews from all relevant module owners will be required.<br />
|owner=[mailto:dcoates@mozilla.com Danny Coates]<br />
|peers=[mailto:vbudhram@mozilla.com Vijay Budhram], [mailto:jhirsch@mozilla.com Jared Hirsch]<br />
|ownersemeritus=[mailto:ryan@rfk.id.au Ryan Kelly]<br />
|peersemeritus=Shane Tomlinson, [mailto:vlad.filippov@gmail.com Vlad Filippov]<br />
|group=<br />
|source_dirs=https://github.com/mozilla/fxa<br />
|mailing list=https://mail.mozilla.org/listinfo/dev-fxacct<br />
|url=https://github.com/mozilla/fxa<br />
}}<br />
<br />
{{Module<br />
|name=Mozilla Location Service (MLS)<br />
|description=The Mozillla Location Service provides a service to position your device based on cell and wireless information.<br />
|owner=[mailto:jwhitlock@mozilla.com John Whitlock]<br />
|ownersemeritus=Hanno Schlighting<br />
|peers=[mailto:wkahngreene@mozilla.com Will Kahn-Greene]<br />
|peersemeritus=Victor Ng (2013-2014), Graydon Hoare (2014)<br />
|forum=https://discourse.mozilla.org/c/location/506<br />
|source_dirs=https://github.com/mozilla/ichnaea<br />
|url=https://location.services.mozilla.com<br />
|components=https://github.com/mozilla/ichnaea/issues, Mozilla Services :: Location<br />
}}<br />
<br />
{{Module<br />
|name=Mozilla Stumbler ("MozStumbler")<br />
|description=The Mozilla Stumbler (MozStumbler) collects wireless network information for crowd-sourcing location positioning with Mozilla Location Service (MLS).<br />
|owner=not set<br />
|peers=[mailto:vng@mozilla.com Victor Ng], [mailto:cpeterson@mozilla.com Chris Peterson]<br />
|forum=https://discourse.mozilla.org/c/location/506<br />
|source_dirs=https://github.com/mozilla/MozStumbler <br />
|url=https://location.services.mozilla.com<br />
|components=https://github.com/mozilla/MozStumbler/issues<br />
}}<br />
<br />
{{Module<br />
|name=Sync<br />
|description=Firefox Sync client<br />
|owner=[mailto:markh@mozilla.com Mark Hammond]<br />
|peers=[mailto:lobailey@mozilla.com Lougenia Bailey], [mailto:teshaq@mozilla.com Tarik Eshaq], [mailto:bdk@mozilla.com Ben Dean-Kawamura], [mailto:skhamis@mozilla.com Sammy Khamis]<br />
|ownersemeritus=[mailto:ryan@rfk.id.au Ryan Kelly]<br />
|group=<br />
|source_dirs=services/sync/<br />
|url=https://wiki.mozilla.org/Services/Process/Code_Review<br />
|components=Sync<br />
}}<br />
<br />
{{Module<br />
|name=Remote Protocol<br />
|description=Low-level remote protocol exposing interfaces for inspecting state and controlling execution of web documents, instrumenting various subsystems in the browser, simulating user interaction for automation purposes, and for subscribing to updates from the aforementioned.<br />
|owner=[mailto:hskupin@mozilla.com Henrik Skupin]<br />
|peers=[mailto:jdescottes@mozilla.com Julian Descottes]<br />
|ownersemeritus=[mailto:ato@sny.no Andreas Tolfsen]<br />
|peersemeritus=[mailto:mfrydrychowicz@mozilla.com Maja Frydrychowicz], [mailto:poirot.alex@gmail.com Alexandre Poirot], [mailto:ystartsev@mozilla.com Yulia Startsev]<br />
|group=dev-remote<br />
|source_dirs=remote/<br />
|url=https://firefox-source-docs.mozilla.org/remote/<br />
|components=Remote Protocol<br />
}}<br />
<br />
{{Module<br />
|name=Rhino<br />
|description=JavaScript interpreter/compiler implemented in Java<br />
|owner=[mailto:greg@apigee.com Greg Brail]<br />
|peers=[mailto:norrisboyd@gmail.com Norris Boyd], [mailto:szegedia@freemail.hu Attila Szegedi]<br />
|group=dev-tech-js-engine<br />
|source_dirs=js/rhino/<br />
|url=http://www.mozilla.org/rhino/<br />
|components=Rhino<br />
}}<br />
<br />
{{Module<br />
|name=URL Classifier<br />
|description=Database and list-based classification of URL resources,<br />
such as Tracking Protection and SafeBrowsing.<br />
|owner=[mailto:dlee@mozilla.com Dimi Lee] (client), [mailto:lcrouch@mozilla.com Luke Crouch] (server)<br />
|peers=[mailto:gcp@mozilla.com Gian-Carlo Pascutto] (client) <br />
|ownersemeritus=François Marier<br />
|peersemeritus=Henry Chang, Ryan Tilder<br />
|group=mozilla.dev.platform<br />
|source_dirs=toolkit/components/url-classifier, netwerk/url-classifier, https://github.com/mozilla-services/shavar<br />
|url=<br />
https://wiki.mozilla.org/Phishing_Protection, https://wiki.mozilla.org/Security/Tracking_protection, https://wiki.mozilla.org/Security/Application_Reputation<br />
|components=<br />
}}<br />
<br />
{{Module<br />
|name=WebCompat Addons <br />
|description=Compatibility interventions (webcompat system addon) and bug reporting capabilities (Report Site Issue addon). <br />
|owner=[mailto:dschubert@mozilla.com Dennis Schubert], [mailto:twisniewski@mozilla.com Thomas Wisniewski]<br />
|peers=[mailto:kberezina@mozilla.com Ksenia Berezina]<br />
|ownersemeritus=Mike Taylor<br />
|group=compatibility@lists.mozilla.org<br />
|source_dirs=browser/extensions/webcompat, browser/extensions/report-site-issue, mobile/android/extensions/webcompat, mobile/android/extensions/report-site-issue, https://github.com/mozilla-extensions/webcompat-addon, https://github.com/mozilla-mobile/android-components/tree/master/components/feature/webcompat-reporter, https://github.com/mozilla-mobile/android-components/tree/master/components/feature/webcompat<br />
|url=https://wiki.mozilla.org/Compatibility/Go_Faster_Addon<br />
|components=Web Compatibility::Interventions, Web Compatibility::Tooling & Investigations<br />
}}</div>Whimboohttps://wiki.mozilla.org/index.php?title=Modules/Testing&diff=1240193Modules/Testing2022-01-24T09:51:01Z<p>Whimboo: Move Maja Frydrychowicz to peer emeritus and add Julian Descottes as peer</p>
<hr />
<div><noinclude><br />
'''Only module owners may edit this page.''' <br />
<br />
They may:<br />
<br />
* update any information about their module except the name of the owner<br />
* add or remove sub-modules<br />
* change the owner of a sub-module <br />
* add emeritus owners or peers<br />
<br />
Other changes, including changes of module owner or addition/removal of modules, must be agreed with the Module Ownership Module group, probably via a discussion in [https://www.mozilla.org/about/forums/#governance mozilla.governance].<br />
</noinclude><br />
{{Module<br />
|name=Mochitest<br />
|description=Mochitest test framework<br />
|owner=[mailto:ahal@mozilla.com Andrew Halberstadt]<br />
|peers=[mailto:jmaher@mozilla.com Joel Maher], [mailto:gbrown@mozilla.com Geoffrey Brown]<br />
|source_dirs=testing/mochitest<br />
|components=Testing :: Mochitest<br />
}}<br />
<br />
{{Module<br />
|name=Reftest (+ jsreftest + crashtest)<br />
|description=Reftest test framework<br />
|owner=[mailto:tnikkel@gmail.com Timothy Nikkel]<br />
|peers=[mailto:jmaher@mozilla.com Joel Maher], [mailto:ahal@mozilla.com Andrew Halbertstadt]<br />
|ownersemeritus=[mailto:dbaron@dbaron.org David Baron]<br />
|peersemeritus=[mailto:jwalden@mit.edu Jeff Walden], [mailto:kgupta@mozilla.staktrace.com Kartikaya Gupta]<br />
|source_dirs=layout/tools/reftest<br />
|components=Testing :: Reftest<br />
}}<br />
<br />
{{Module<br />
|name=web-platform-tests infrastructure<br />
|description=web-platform-tests test framework<br />
|description=Infrastructure for running the cross-browser web-platform-tests suite<br />
|owner=[mailto:james@hoppipolla.co.uk James Graham]<br />
|peers=[mailto:maja@mozilla.com Maja Frydrychowicz]<br />
|peersemeritus=[mailto:ato@sny.no Andreas Tolfsen]<br />
|source_dirs=testing/web-platform excluding testing/web-platform/tests, testing/web-platform/meta and testing/web-platform/mozilla, but including testing/web-platform/tests/tools<br />
|components=Testing :: web-platform-tests<br />
}}<br />
<br />
{{Module<br />
|name=geckodriver<br />
|description=Proxy for using W3C WebDriver-compatible clients to interact with Gecko-based browsers.<br />
|owner=[mailto:james@hoppipolla.co.uk James Graham]<br />
|peers=[mailto:hskupin@mozilla.com Henrik Skupin], <br />
|ownersemeritus=[mailto:ato@sny.no Andreas Tolfsen]<br />
|peersemeritus=[mailto:dburns@mozilla.com David Burns], <br />
|source_dirs=testing/geckodriver<br />
|components=Testing :: geckodriver<br />
}}<br />
<br />
{{Module<br />
|name=Marionette<br />
|description=Marionette is a remote protocol that lets out-of-process programs communicate with, instrument, and control Gecko-based browsers. Combined with geckodriver, this forms our WebDriver implementation.<br />
|owner=[mailto:hskupin@mozilla.com Henrik Skupin],<br />
|peers=[mailto:jdescottes@mozilla.com Julian Descottes], [mailto:james@hoppipolla.co.uk James Graham]<br />
|ownersemeritus=[mailto:ato@sny.no Andreas Tolfsen]<br />
|peersemeritus=[mailto:maja@mozilla.com Maja Frydrychowicz], [mailto:dburns@mozilla.com David Burns], <br />
|source_dirs=testing/marionette<br />
|components=Testing :: Marionette<br />
}}<br />
<br />
{{Module<br />
|name=firefox-ui<br />
|description=Firefox UI test framework<br />
|owner=[mailto:hskupin@mozilla.com Henrik Skupin]<br />
|peers=[mailto:jdescottes@mozilla.com Julian Descottes]<br />
|peersemeritus=[mailto:maja@mozilla.com Maja Frydrychowicz], <br />
|source_dirs=testing/firefox-ui<br />
|components=Testing :: Firefox UI<br />
}}<br />
<br />
{{Module<br />
|name=Performance Testing<br />
|description=This module encompasses all of our performance test frameworks: Raptor, Talos, MozPerfTest, AWSY<br />
|owner=[mailto:gmierzwinski@mozilla.com Greg Mierzwinski]<br />
|peers=[mailto:ksereduck@mozilla.com Kimberly Sereduck]<br />
|source_dirs=testing/raptor, testing/talos, python/mozperftest, testing/awsy<br />
|components=Testing :: Raptor, Testing :: Talos, Testing :: AWSY, Testing :: Performance<br />
}}<br />
<br />
{{Module<br />
|name=XPCShell<br />
|description=XPCShell test harness<br />
|owner=[mailto:jmaher@mozilla.com Joel Maher]<br />
|peers=[mailto:gbrown@mozilla.com Geoffrey Brown]<br />
|source_dirs=testing/xpcshell<br />
|components=Testing::XPCShell Harness<br />
}}<br />
<br />
{{Module<br />
|name=gtest<br />
|description=GTest test harness<br />
|owner=[mailto:gbrown@mozilla.com Geoffrey Brown]<br />
|source_dirs=testing/gtest<br />
|components=Testing :: GTest<br />
}}<br />
<br />
{{Module<br />
|name=Mozbase<br />
|description=Base modules used for implementing test components<br />
|owner=[mailto:gbrown@mozilla.com Geoffrey Brown]<br />
|peers=[mailto:ahal@mozilla.com Andrew Halberstadt], [mailto:ato@sny.no Andreas Tolfsen], [mailto:bob@bclary.com Bob Clary], [mailto:james@hoppipolla.co.uk James Graham], [mailto:hskupin@mozilla.com Henrik Skupin]<br />
|components=Testing :: Mozbase, Testing :: Mozbase Rust<br />
}}<br />
<br />
{{Module<br />
|name=Tryselect<br />
|description=Frontend for selecting jobs on the try server<br />
|owner=[mailto:ahal@mozilla.com Andrew Halberstadt]<br />
|peers=[mailto:james@hoppipolla.co.uk James Graham]<br />
|source_dirs=tools/tryselect<br />
|components=Firefox Build System :: Try<br />
}}<br />
<br />
{{Module<br />
|name=mozharness<br />
|description=Configuration-driven script harness<br />
|owner=[mailto:asasaki@mozilla.com Aki Sasaki]<br />
|peers=[mailto:callek@gmail.com Justin Wood], [mailto:mozilla@hocat.ca Tom Prince]<br />
|source_dirs=testing/mozharness<br />
|components=Release Engineering :: Applications: MozharnessCore<br />
}}</div>Whimboohttps://wiki.mozilla.org/index.php?title=WebDriver/Meetings&diff=1239800WebDriver/Meetings2022-01-03T13:26:45Z<p>Whimboo: Final archive for meeting notes</p>
<hr />
<div>== Meetings ==<br />
Our team holds different public meetings throughout the week. If you are interested we encourage you to join them. <br />
<br />
=== WebDriver Project ===<br />
This meeting happens [https://arewemeetingyet.com/UTC/2021-02-15/14:30/w/WebDriver Mondays at 2:30pm UTC]. We meet in the '''WebDriver''' [https://mozilla.zoom.us/j/92770467592 Zoom] room, but you can also [https://applications.zoom.us/addon/invitation/detail?meetingUuid=mxZpMi0lQfaMFeSrShocVA%3D%3D&signature=08b679297c0998c1970bb623dc67d13e095058fd6daa4be481393f5848ea55b0&v=1 join via telephone].<br />
<br />
Meeting notes will be archived and can be found here:<br />
* [https://docs.google.com/document/d/1MZ24bY9v0vvL0K-atO3f9PrFpZX28FIpqqMLY7uCpMs/ 2022]<br />
* [https://docs.google.com/document/d/1y1gFvTwpypc3rk7yCVOe1dZcMHFvX38MQfctllqs19A/edit#heading=h.b2acla2sb01r 2021]<br />
* [[WebDriver/Meetings/Archive|Archive (2014 - 2019)]]<br />
<br />
=== WebDriver Triage ===<br />
This meeting happens [https://arewemeetingyet.com/UTC/2021-02-15/14:00/w/WebDriver_Triage Mondays at 2:00pm UTC]. We meet in the '''WebDriver Triage''' [https://mozilla.zoom.us/j/92698041501 Zoom] room, but you can also [https://applications.zoom.us/addon/invitation/detail?meetingUuid=XMQbx4StSKy6w5DsmlQLNw%3D%3D&signature=0dd3d27a2672f80a2f55b26a4774b50402db6778370b752d1449d0175ab0741f&v=1 join via telephone].<br />
<br />
Meeting notes will be archived and can be found here:<br />
* [https://docs.google.com/document/d/1t45TF5QLaWhaxoHTdmfcBF2gT8sKmYdWFp0zEFRzaKw/ 2022]<br />
* [https://docs.google.com/document/d/1h5vdtS0SeOlD95wetbiIRwyMR84ZzCWlGhNi7U0-DPo/ 2021]</div>Whimboohttps://wiki.mozilla.org/index.php?title=WebDriver/Meetings&diff=1239799WebDriver/Meetings2022-01-03T13:22:59Z<p>Whimboo: Link to Remote Protocol meetings</p>
<hr />
<div>== Meetings ==<br />
Our team holds different public meetings throughout the week. If you are interested we encourage you to join them. <br />
<br />
=== WebDriver Project ===<br />
This meeting happens [https://arewemeetingyet.com/UTC/2021-02-15/14:30/w/WebDriver Mondays at 2:30pm UTC]. We meet in the '''WebDriver''' [https://mozilla.zoom.us/j/92770467592 Zoom] room, but you can also [https://applications.zoom.us/addon/invitation/detail?meetingUuid=mxZpMi0lQfaMFeSrShocVA%3D%3D&signature=08b679297c0998c1970bb623dc67d13e095058fd6daa4be481393f5848ea55b0&v=1 join via telephone].<br />
<br />
Meeting notes will be archived and can be found here:<br />
* [https://docs.google.com/document/d/1MZ24bY9v0vvL0K-atO3f9PrFpZX28FIpqqMLY7uCpMs/ 2022]<br />
* [https://docs.google.com/document/d/1y1gFvTwpypc3rk7yCVOe1dZcMHFvX38MQfctllqs19A/edit#heading=h.b2acla2sb01r 2021]<br />
* [[WebDriver/RemoteProtocol/Meetings|2019 - 2020]]<br />
* [[Archive|Archive (2014 - 2018)]]<br />
<br />
=== WebDriver Triage ===<br />
This meeting happens [https://arewemeetingyet.com/UTC/2021-02-15/14:00/w/WebDriver_Triage Mondays at 2:00pm UTC]. We meet in the '''WebDriver Triage''' [https://mozilla.zoom.us/j/92698041501 Zoom] room, but you can also [https://applications.zoom.us/addon/invitation/detail?meetingUuid=XMQbx4StSKy6w5DsmlQLNw%3D%3D&signature=0dd3d27a2672f80a2f55b26a4774b50402db6778370b752d1449d0175ab0741f&v=1 join via telephone].<br />
<br />
Meeting notes will be archived and can be found here:<br />
* [https://docs.google.com/document/d/1t45TF5QLaWhaxoHTdmfcBF2gT8sKmYdWFp0zEFRzaKw/ 2022]<br />
* [https://docs.google.com/document/d/1h5vdtS0SeOlD95wetbiIRwyMR84ZzCWlGhNi7U0-DPo/ 2021]</div>Whimboohttps://wiki.mozilla.org/index.php?title=WebDriver/Meetings&diff=1239798WebDriver/Meetings2022-01-03T13:16:12Z<p>Whimboo: /* WebDriver Triage */ New document for 2022</p>
<hr />
<div>== Meetings ==<br />
Our team holds different public meetings throughout the week. If you are interested we encourage you to join them. <br />
<br />
=== WebDriver Project ===<br />
This meeting happens [https://arewemeetingyet.com/UTC/2021-02-15/14:30/w/WebDriver Mondays at 2:30pm UTC]. We meet in the '''WebDriver''' [https://mozilla.zoom.us/j/92770467592 Zoom] room, but you can also [https://applications.zoom.us/addon/invitation/detail?meetingUuid=mxZpMi0lQfaMFeSrShocVA%3D%3D&signature=08b679297c0998c1970bb623dc67d13e095058fd6daa4be481393f5848ea55b0&v=1 join via telephone].<br />
<br />
Meeting notes will be archived and can be found here:<br />
* [https://docs.google.com/document/d/1MZ24bY9v0vvL0K-atO3f9PrFpZX28FIpqqMLY7uCpMs/ 2022]<br />
* [https://docs.google.com/document/d/1y1gFvTwpypc3rk7yCVOe1dZcMHFvX38MQfctllqs19A/edit#heading=h.b2acla2sb01r 2021]<br />
* [[Archive|Archive (2014 - 2020)]]<br />
<br />
=== WebDriver Triage ===<br />
This meeting happens [https://arewemeetingyet.com/UTC/2021-02-15/14:00/w/WebDriver_Triage Mondays at 2:00pm UTC]. We meet in the '''WebDriver Triage''' [https://mozilla.zoom.us/j/92698041501 Zoom] room, but you can also [https://applications.zoom.us/addon/invitation/detail?meetingUuid=XMQbx4StSKy6w5DsmlQLNw%3D%3D&signature=0dd3d27a2672f80a2f55b26a4774b50402db6778370b752d1449d0175ab0741f&v=1 join via telephone].<br />
<br />
Meeting notes will be archived and can be found here:<br />
* [https://docs.google.com/document/d/1t45TF5QLaWhaxoHTdmfcBF2gT8sKmYdWFp0zEFRzaKw/ 2022]<br />
* [https://docs.google.com/document/d/1h5vdtS0SeOlD95wetbiIRwyMR84ZzCWlGhNi7U0-DPo/ 2021]</div>Whimboohttps://wiki.mozilla.org/index.php?title=WebDriver/Meetings&diff=1239797WebDriver/Meetings2022-01-03T13:09:36Z<p>Whimboo: New meeting document for 2022</p>
<hr />
<div>== Meetings ==<br />
Our team holds different public meetings throughout the week. If you are interested we encourage you to join them. <br />
<br />
=== WebDriver Project ===<br />
This meeting happens [https://arewemeetingyet.com/UTC/2021-02-15/14:30/w/WebDriver Mondays at 2:30pm UTC]. We meet in the '''WebDriver''' [https://mozilla.zoom.us/j/92770467592 Zoom] room, but you can also [https://applications.zoom.us/addon/invitation/detail?meetingUuid=mxZpMi0lQfaMFeSrShocVA%3D%3D&signature=08b679297c0998c1970bb623dc67d13e095058fd6daa4be481393f5848ea55b0&v=1 join via telephone].<br />
<br />
Meeting notes will be archived and can be found here:<br />
* [https://docs.google.com/document/d/1MZ24bY9v0vvL0K-atO3f9PrFpZX28FIpqqMLY7uCpMs/ 2022]<br />
* [https://docs.google.com/document/d/1y1gFvTwpypc3rk7yCVOe1dZcMHFvX38MQfctllqs19A/edit#heading=h.b2acla2sb01r 2021]<br />
* [[Archive|Archive (2014 - 2020)]]<br />
<br />
=== WebDriver Triage ===<br />
This meeting happens [https://arewemeetingyet.com/UTC/2021-02-15/14:00/w/WebDriver_Triage Mondays at 2:00pm UTC]. We meet in the '''WebDriver Triage''' [https://mozilla.zoom.us/j/92698041501 Zoom] room, but you can also [https://applications.zoom.us/addon/invitation/detail?meetingUuid=XMQbx4StSKy6w5DsmlQLNw%3D%3D&signature=0dd3d27a2672f80a2f55b26a4774b50402db6778370b752d1449d0175ab0741f&v=1 join via telephone].<br />
<br />
Meeting notes will be archived and can be found here:<br />
* [https://docs.google.com/document/d/1h5vdtS0SeOlD95wetbiIRwyMR84ZzCWlGhNi7U0-DPo/edit# 2021]</div>Whimboohttps://wiki.mozilla.org/index.php?title=WebDriver/RemoteProtocol/WebDriver_BiDi&diff=1239689WebDriver/RemoteProtocol/WebDriver BiDi2021-12-22T11:00:53Z<p>Whimboo: Milestone 3 added</p>
<hr />
<div>[https://w3c.github.io/webdriver-bidi WebDriver BiDi] is an extension of the [https://w3c.github.io/webdriver/ WebDriver specification] that offers a bidirectional communication between a webdriver compatible client and a remote end like Firefox. That means that beside sending commands to the browser and receiving responses, it will be also possible to register for certain events (e.g page load, network interception).<br />
<br />
== Project Status ==<br />
=== WebDriver BiDi Milestone 3 (required) ===<br />
'''Goal''': Basic support for the browsingContext.navigate command, and collaboration with the Selenium project to get log.entryAdded support added.<br />
<br />
<bugzilla><br />
{<br />
"whiteboard": "[bidi-m3-mvp]",<br />
"priority":["P1","P2"], <br />
"include_fields":"id, summary, status, assigned_to, priority, cf_fx_points"<br />
}<br />
</bugzilla><br />
<br />
=== WebDriver BiDi Milestone 3 (reserved) ===<br />
<bugzilla><br />
{<br />
"whiteboard": "[bidi-m3-mvp]", <br />
"priority":["P3"], <br />
"include_fields":"id, summary, status, assigned_to, priority, cf_fx_points"<br />
}<br />
</bugzilla><br />
<br />
=== WebDriver BiDi Milestone 2 (completed - 12/19/21) ===<br />
'''Goal''': Extend the current WebDriver BiDi code base to fully support log.entryAdded events and allow clients to unsubscribe from this event.<br />
<br />
<bugzilla><br />
{<br />
"whiteboard": "[bidi-m2-mvp]",<br />
"priority":["P1","P2"], <br />
"include_fields":"id, summary, status, assigned_to, priority, cf_fx_points"<br />
}<br />
</bugzilla><br />
<br />
=== WebDriver BiDi Milestone 1 (completed - 09/10/21) ===<br />
'''Goal''': Adapt the existing Remote Agent code base, and make it ready for building support for WebDriver BiDi. Introduce support for basic logging events (plain string message).<br />
<br />
This milestone has been completed on September 10th, 2021.<br />
<br />
<bugzilla><br />
{<br />
"whiteboard": "[bidi-m1-mvp]",<br />
"priority":["P1","P2"], <br />
"include_fields":"id, summary, status, assigned_to, priority, cf_fx_points"<br />
}<br />
</bugzilla></div>Whimboohttps://wiki.mozilla.org/index.php?title=WebDriver/RemoteProtocol/WebDriver_BiDi&diff=1237930WebDriver/RemoteProtocol/WebDriver BiDi2021-09-13T19:45:04Z<p>Whimboo: /* WebDriver BiDi Milestone 2 (required) */ Updated goals</p>
<hr />
<div>[https://w3c.github.io/webdriver-bidi WebDriver BiDi] is an extension of the [https://w3c.github.io/webdriver/ WebDriver specification] that offers a bidirectional communication between a webdriver compatible client and a remote end like Firefox. That means that beside sending commands to the browser and receiving responses, it will be also possible to register for certain events (e.g page load, network interception).<br />
<br />
== Project Status ==<br />
=== WebDriver BiDi Milestone 2 (required) ===<br />
'''Goal''': Extend the current WebDriver BiDi code base to allow external clients to connect to Firefox and to run the first completed BiDi event for logging. Further add basic functionality for navigation.<br />
<br />
<bugzilla><br />
{<br />
"whiteboard": "[bidi-m2-mvp]",<br />
"priority":["P1","P2"], <br />
"include_fields":"id, summary, status, assigned_to, priority, cf_fx_points"<br />
}<br />
</bugzilla><br />
<br />
=== WebDriver BiDi Milestone 2 (reserved) ===<br />
<bugzilla><br />
{<br />
"whiteboard": "[bidi-m2-mvp]", <br />
"priority":["P3"], <br />
"include_fields":"id, summary, status, assigned_to, priority, cf_fx_points"<br />
}<br />
</bugzilla><br />
<br />
=== WebDriver BiDi Milestone 1 (completed - 09/10/21) ===<br />
'''Goal''': Adapt the existing Remote Agent code base, and make it ready for building support for WebDriver BiDi. Introduce support for basic logging events (plain string message).<br />
<br />
This milestone has been completed on September 10th, 2021.<br />
<br />
<bugzilla><br />
{<br />
"whiteboard": "[bidi-m1-mvp]",<br />
"priority":["P1","P2"], <br />
"include_fields":"id, summary, status, assigned_to, priority, cf_fx_points"<br />
}<br />
</bugzilla></div>Whimboohttps://wiki.mozilla.org/index.php?title=WebDriver&diff=1237921WebDriver2021-09-13T07:14:33Z<p>Whimboo: /* Communication */ Update to webdriver Element channel</p>
<hr />
<div>WebDriver is a remote control interface<br />
that enables introspection and control of user agents.<br />
It provides a platform- and language-neutral wire protocol<br />
as a way for out-of-process programs<br />
to remotely instruct the behavior of web browsers.<br />
<br />
'''This is the project page for the WebDriver project at Mozilla.'''<br />
If you’re looking for [https://developer.mozilla.org/en-US/docs/Web/WebDriver information about WebDriver itself you will find that on MDN].<br />
<br />
== Components ==<br />
The implementation of WebDriver in Firefox consists of different layers with each of them handled by it's own component.<br />
<br />
=== Marionette ===<br />
[[WebDriver/Marionette|Marionette]] is a remote protocol that lets out-of-process programs communicate with, instrument, and control Gecko-based browsers. It implements the [https://w3c.github.io/webdriver/ WebDriver specification], which is then made available via a custom socket protocol to geckodriver.<br />
<br />
It provides interfaces for interacting with both the internal JavaScript runtime and UI elements of Gecko-based browsers, such as Firefox and Fenix. It can control both the content and chrome- documents, giving a high level of control and ability to emulate user interaction.<br />
<br />
=== geckodriver ===<br />
[[WebDriver/geckodriver|geckodriver]] is a proxy for using W3C WebDriver-compatible clients to interact with Gecko-based browsers.<br />
<br />
This program provides the HTTP API described by the [https://w3c.github.io/webdriver/ WebDriver specification] to communicate with Gecko browsers. It translates calls into the [[WebDriver/Marionette|Marionette]] compatible remote protocol by acting as a proxy between the local- and remote ends.<br />
<br />
=== Remote Protocol ===<br />
The Firefox [[WebDriver/RemoteProtocol|Remote Protocol]] is a low-level debugging interface you can use to inspect the state and control execution of documents running in web content, instrument the browser in interesting ways, simulate user interaction for automation purposes, and for subscribing to events in the browser such as network- or console logs.<br />
<br />
It's primary purpose is the implementation of the [https://w3c.github.io/webdriver-bidi/ WebDriver BiDi specification]. But it also complements the existing Firefox Developer Tools [https://firefox-source-docs.mozilla.org/devtools/backend/protocol.html#remote-debugging-protocol Remote Debugging Protocol (RDP)] by implementing a subset of the [https://chromedevtools.github.io/devtools-protocol/ Chrome DevTools Protocol (CDP)].<br />
<br />
== Communication ==<br />
<br />
; Mailing list<br />
: [http://mailto:dev-webdriver@mozilla.org dev-webdriver@mozilla.org] ([https://groups.google.com/a/mozilla.org/g/dev-webdriver subscribe])<br />
; Real-time chat<br />
: The communication channel for the team is [https://chat.mozilla.org/#/room/#webdriver:mozilla.org Element/#webdriver].<br />
; Bug tracking<br />
: [https://bugzilla.mozilla.org/buglist.cgi?product=Testing&component=Marionette&resolution=--- WebDriver (Marionette) in Bugzilla]<br />
: [https://bugzilla.mozilla.org/buglist.cgi?product=Remote%20Protocol&component=WebDriver%20BiDi&resolution=--- WebDriver BiDi in Bugzilla]<br />
: [https://bugzilla.mozilla.org/buglist.cgi?product=Testing&component=geckodriver&resolution=--- geckodriver in Bugzilla]<br />
: [https://github.com/mozilla/geckodriver geckodriver on GitHub]<br />
: [https://bugzilla.mozilla.org/buglist.cgi?product=Testing&component=Mozbase%20Rust&resolution=--- Rust port of mozbase]<br />
<br />
== Staff ==<br />
* Jan Odvarko (honza), manager<br />
* [https://www.hskupin.info/ Henrik Skupin] (whimboo), engineer<br />
* Julian Descottes (jdescottes), engineer<br />
* [https://hoppipolla.co.uk/ James Graham] (jgraham), engineer (WebDriver Spec)<br />
* Marco Mucci (mmucci), EPM<br />
<br />
== Meetings ==<br />
The team has a public meetings on Mondays at 2:30 pm UTC.<br />
<br />
* See [[WebDriver/Meetings]] for more details and minutes</div>Whimboohttps://wiki.mozilla.org/index.php?title=WebDriver/RemoteProtocol/WebDriver_BiDi&diff=1237920WebDriver/RemoteProtocol/WebDriver BiDi2021-09-13T07:11:52Z<p>Whimboo: Added completion date</p>
<hr />
<div>[https://w3c.github.io/webdriver-bidi WebDriver BiDi] is an extension of the [https://w3c.github.io/webdriver/ WebDriver specification] that offers a bidirectional communication between a webdriver compatible client and a remote end like Firefox. That means that beside sending commands to the browser and receiving responses, it will be also possible to register for certain events (e.g page load, network interception).<br />
<br />
== Project Status ==<br />
=== WebDriver BiDi Milestone 2 (required) ===<br />
'''Goal''': Extend low-level code to prepare the implementation for the next BiDi features, and allow the Selenium project to start implementing the first BiDi feature (log.entryAdded). Further implement basic support for ''browsingContext.navigate''.<br />
<br />
<bugzilla><br />
{<br />
"whiteboard": "[bidi-m2-mvp]",<br />
"priority":["P1","P2"], <br />
"include_fields":"id, summary, status, assigned_to, priority, cf_fx_points"<br />
}<br />
</bugzilla><br />
<br />
=== WebDriver BiDi Milestone 2 (reserved) ===<br />
<bugzilla><br />
{<br />
"whiteboard": "[bidi-m2-mvp]", <br />
"priority":["P3"], <br />
"include_fields":"id, summary, status, assigned_to, priority, cf_fx_points"<br />
}<br />
</bugzilla><br />
<br />
=== WebDriver BiDi Milestone 1 (completed - 09/10/21) ===<br />
'''Goal''': Adapt the existing Remote Agent code base, and make it ready for building support for WebDriver BiDi. Introduce support for basic logging events (plain string message).<br />
<br />
This milestone has been completed on September 10th, 2021.<br />
<br />
<bugzilla><br />
{<br />
"whiteboard": "[bidi-m1-mvp]",<br />
"priority":["P1","P2"], <br />
"include_fields":"id, summary, status, assigned_to, priority, cf_fx_points"<br />
}<br />
</bugzilla></div>Whimboohttps://wiki.mozilla.org/index.php?title=WebDriver/RemoteProtocol/WebDriver_BiDi&diff=1237919WebDriver/RemoteProtocol/WebDriver BiDi2021-09-13T07:10:49Z<p>Whimboo: milestone 1 is completed</p>
<hr />
<div>[https://w3c.github.io/webdriver-bidi WebDriver BiDi] is an extension of the [https://w3c.github.io/webdriver/ WebDriver specification] that offers a bidirectional communication between a webdriver compatible client and a remote end like Firefox. That means that beside sending commands to the browser and receiving responses, it will be also possible to register for certain events (e.g page load, network interception).<br />
<br />
== Project Status ==<br />
=== WebDriver BiDi Milestone 2 (required) ===<br />
'''Goal''': Extend low-level code to prepare the implementation for the next BiDi features, and allow the Selenium project to start implementing the first BiDi feature (log.entryAdded). Further implement basic support for ''browsingContext.navigate''.<br />
<br />
<bugzilla><br />
{<br />
"whiteboard": "[bidi-m2-mvp]",<br />
"priority":["P1","P2"], <br />
"include_fields":"id, summary, status, assigned_to, priority, cf_fx_points"<br />
}<br />
</bugzilla><br />
<br />
=== WebDriver BiDi Milestone 2 (reserved) ===<br />
<bugzilla><br />
{<br />
"whiteboard": "[bidi-m2-mvp]", <br />
"priority":["P3"], <br />
"include_fields":"id, summary, status, assigned_to, priority, cf_fx_points"<br />
}<br />
</bugzilla><br />
<br />
=== WebDriver BiDi Milestone 1 (completed) ===<br />
'''Goal''': Adapt the existing Remote Agent code base, and make it ready for building support for WebDriver BiDi. Introduce support for basic logging events (plain string message).<br />
<br />
<bugzilla><br />
{<br />
"whiteboard": "[bidi-m1-mvp]",<br />
"priority":["P1","P2"], <br />
"include_fields":"id, summary, status, assigned_to, priority, cf_fx_points"<br />
}<br />
</bugzilla></div>Whimboohttps://wiki.mozilla.org/index.php?title=WebDriver/RemoteProtocol/WebDriver_BiDi&diff=1237918WebDriver/RemoteProtocol/WebDriver BiDi2021-09-13T07:10:26Z<p>Whimboo: Just use milestone 1 without reserved information</p>
<hr />
<div>[https://w3c.github.io/webdriver-bidi WebDriver BiDi] is an extension of the [https://w3c.github.io/webdriver/ WebDriver specification] that offers a bidirectional communication between a webdriver compatible client and a remote end like Firefox. That means that beside sending commands to the browser and receiving responses, it will be also possible to register for certain events (e.g page load, network interception).<br />
<br />
== Project Status ==<br />
=== WebDriver BiDi Milestone 2 (required) ===<br />
'''Goal''': Extend low-level code to prepare the implementation for the next BiDi features, and allow the Selenium project to start implementing the first BiDi feature (log.entryAdded). Further implement basic support for ''browsingContext.navigate''.<br />
<br />
<bugzilla><br />
{<br />
"whiteboard": "[bidi-m2-mvp]",<br />
"priority":["P1","P2"], <br />
"include_fields":"id, summary, status, assigned_to, priority, cf_fx_points"<br />
}<br />
</bugzilla><br />
<br />
=== WebDriver BiDi Milestone 2 (reserved) ===<br />
<bugzilla><br />
{<br />
"whiteboard": "[bidi-m2-mvp]", <br />
"priority":["P3"], <br />
"include_fields":"id, summary, status, assigned_to, priority, cf_fx_points"<br />
}<br />
</bugzilla><br />
<br />
=== WebDriver BiDi Milestone 1 ===<br />
'''Goal''': Adapt the existing Remote Agent code base, and make it ready for building support for WebDriver BiDi. Introduce support for basic logging events (plain string message).<br />
<br />
<bugzilla><br />
{<br />
"whiteboard": "[bidi-m1-mvp]",<br />
"priority":["P1","P2"], <br />
"include_fields":"id, summary, status, assigned_to, priority, cf_fx_points"<br />
}<br />
</bugzilla></div>Whimboohttps://wiki.mozilla.org/index.php?title=WebDriver/RemoteProtocol/WebDriver_BiDi&diff=1237917WebDriver/RemoteProtocol/WebDriver BiDi2021-09-13T07:08:46Z<p>Whimboo: Remove unused milestone 1 reserved bug list</p>
<hr />
<div>[https://w3c.github.io/webdriver-bidi WebDriver BiDi] is an extension of the [https://w3c.github.io/webdriver/ WebDriver specification] that offers a bidirectional communication between a webdriver compatible client and a remote end like Firefox. That means that beside sending commands to the browser and receiving responses, it will be also possible to register for certain events (e.g page load, network interception).<br />
<br />
== Project Status ==<br />
=== WebDriver BiDi Milestone 2 (required) ===<br />
'''Goal''': Extend low-level code to prepare the implementation for the next BiDi features, and allow the Selenium project to start implementing the first BiDi feature (log.entryAdded). Further implement basic support for ''browsingContext.navigate''.<br />
<br />
<bugzilla><br />
{<br />
"whiteboard": "[bidi-m2-mvp]",<br />
"priority":["P1","P2"], <br />
"include_fields":"id, summary, status, assigned_to, priority, cf_fx_points"<br />
}<br />
</bugzilla><br />
<br />
=== WebDriver BiDi Milestone 2 (reserved) ===<br />
<bugzilla><br />
{<br />
"whiteboard": "[bidi-m2-mvp]", <br />
"priority":["P3"], <br />
"include_fields":"id, summary, status, assigned_to, priority, cf_fx_points"<br />
}<br />
</bugzilla><br />
<br />
=== WebDriver BiDi Milestone 1 (required) ===<br />
'''Goal''': Adapt the existing Remote Agent code base, and make it ready for building support for WebDriver BiDi. Introduce support for basic logging events (plain string message).<br />
<br />
<bugzilla><br />
{<br />
"whiteboard": "[bidi-m1-mvp]",<br />
"priority":["P1","P2"], <br />
"include_fields":"id, summary, status, assigned_to, priority, cf_fx_points"<br />
}<br />
</bugzilla></div>Whimboohttps://wiki.mozilla.org/index.php?title=WebDriver/RemoteProtocol/WebDriver_BiDi&diff=1237916WebDriver/RemoteProtocol/WebDriver BiDi2021-09-13T07:08:05Z<p>Whimboo: /* Project Status */ Adding milestone 2 section</p>
<hr />
<div>[https://w3c.github.io/webdriver-bidi WebDriver BiDi] is an extension of the [https://w3c.github.io/webdriver/ WebDriver specification] that offers a bidirectional communication between a webdriver compatible client and a remote end like Firefox. That means that beside sending commands to the browser and receiving responses, it will be also possible to register for certain events (e.g page load, network interception).<br />
<br />
== Project Status ==<br />
=== WebDriver BiDi Milestone 2 (required) ===<br />
'''Goal''': Extend low-level code to prepare the implementation for the next BiDi features, and allow the Selenium project to start implementing the first BiDi feature (log.entryAdded). Further implement basic support for ''browsingContext.navigate''.<br />
<br />
<bugzilla><br />
{<br />
"whiteboard": "[bidi-m2-mvp]",<br />
"priority":["P1","P2"], <br />
"include_fields":"id, summary, status, assigned_to, priority, cf_fx_points"<br />
}<br />
</bugzilla><br />
<br />
=== WebDriver BiDi Milestone 2 (reserved) ===<br />
<bugzilla><br />
{<br />
"whiteboard": "[bidi-m2-mvp]", <br />
"priority":["P3"], <br />
"include_fields":"id, summary, status, assigned_to, priority, cf_fx_points"<br />
}<br />
</bugzilla><br />
<br />
=== WebDriver BiDi Milestone 1 (required) ===<br />
'''Goal''': Adapt the existing Remote Agent code base, and make it ready for building support for WebDriver BiDi. Introduce support for basic logging events (plain string message).<br />
<br />
<bugzilla><br />
{<br />
"whiteboard": "[bidi-m1-mvp]",<br />
"priority":["P1","P2"], <br />
"include_fields":"id, summary, status, assigned_to, priority, cf_fx_points"<br />
}<br />
</bugzilla><br />
<br />
=== WebDriver BiDi Milestone 1 (reserved) ===<br />
<bugzilla><br />
{<br />
"whiteboard": "[bidi-m1-mvp]", <br />
"priority":["P3"], <br />
"include_fields":"id, summary, status, assigned_to, priority, cf_fx_points"<br />
}<br />
</bugzilla></div>Whimboohttps://wiki.mozilla.org/index.php?title=WebDriver/RemoteProtocol/WebDriver_BiDi&diff=1236666WebDriver/RemoteProtocol/WebDriver BiDi2021-07-14T09:22:40Z<p>Whimboo: /* WebDriver BiDi Milestone 1 (required) */ updated goal for basic logging events</p>
<hr />
<div>[https://w3c.github.io/webdriver-bidi WebDriver BiDi] is an extension of the [https://w3c.github.io/webdriver/ WebDriver specification] that offers a bidirectional communication between a webdriver compatible client and a remote end like Firefox. That means that beside sending commands to the browser and receiving responses, it will be also possible to register for certain events (e.g page load, network interception).<br />
<br />
If you find a bug with Fission enabled please file a bug under [https://bugzilla.mozilla.org/enter_bug.cgi?product=Remote%20Protocol&component=WebDriver%20BiDi Remote Protocol :: WebDriver BiDi].<br />
<br />
== Project Status ==<br />
=== WebDriver BiDi Milestone 1 (required) ===<br />
'''Goal''': Adapt the existing Remote Agent code base, and make it ready for building support for WebDriver BiDi. Introduce support for basic logging events (plain string message).<br />
<br />
<bugzilla><br />
{<br />
"whiteboard": "[bidi-m1-mvp]",<br />
"priority":["P1","P2"], <br />
"include_fields":"id, summary, status, assigned_to, priority, cf_fx_points"<br />
}<br />
</bugzilla><br />
<br />
=== WebDriver BiDi Milestone 1 (reserved) ===<br />
<bugzilla><br />
{<br />
"whiteboard": "[bidi-m1-mvp]", <br />
"priority":["P3"], <br />
"include_fields":"id, summary, status, assigned_to, priority, cf_fx_points"<br />
}<br />
</bugzilla></div>Whimboohttps://wiki.mozilla.org/index.php?title=WebDriver/RemoteProtocol/WebDriver_BiDi&diff=1236662WebDriver/RemoteProtocol/WebDriver BiDi2021-07-14T09:21:47Z<p>Whimboo: /* Project Status */ Added M1 goal</p>
<hr />
<div>[https://w3c.github.io/webdriver-bidi WebDriver BiDi] is an extension of the [https://w3c.github.io/webdriver/ WebDriver specification] that offers a bidirectional communication between a webdriver compatible client and a remote end like Firefox. That means that beside sending commands to the browser and receiving responses, it will be also possible to register for certain events (e.g page load, network interception).<br />
<br />
If you find a bug with Fission enabled please file a bug under [https://bugzilla.mozilla.org/enter_bug.cgi?product=Remote%20Protocol&component=WebDriver%20BiDi Remote Protocol :: WebDriver BiDi].<br />
<br />
== Project Status ==<br />
=== WebDriver BiDi Milestone 1 (required) ===<br />
'''Goal''': Adapt the existing Remote Agent code base, and make it ready for building support for WebDriver BiDi. Introduce support for Logging events.<br />
<br />
<bugzilla><br />
{<br />
"whiteboard": "[bidi-m1-mvp]",<br />
"priority":["P1","P2"], <br />
"include_fields":"id, summary, status, assigned_to, priority, cf_fx_points"<br />
}<br />
</bugzilla><br />
<br />
=== WebDriver BiDi Milestone 1 (reserved) ===<br />
<bugzilla><br />
{<br />
"whiteboard": "[bidi-m1-mvp]", <br />
"priority":["P3"], <br />
"include_fields":"id, summary, status, assigned_to, priority, cf_fx_points"<br />
}<br />
</bugzilla></div>Whimboo