Open Bug 1750210 Opened 3 years ago Updated 3 years ago

Extract application specific logic from browser.js in dedicated modules

Categories

(Remote Protocol :: Agent, task, P3)

Product:
Remote Protocol
Component:
Agent
Type:
task

Tracking

(Not tracked)

People

(Reporter: jdescottes, Unassigned)

References

Details

Initially filed to ship remote/shared/MobileTabBrowser.jsm only on ANDROID builds, we are repurposing this bug to split the current browser.js logic in several application specific modules, and only include the relevant modules for the application being built.

In this context, application refers for instance to "desktop firefox", "mobile firefox", "thunderbird"

Note that currently browser.js is quite small (https://searchfox.org/mozilla-central/rev/fa48ebee58d59fa846919c3e2c3122b08db57c9c/testing/marionette/browser.js) but we might add more application specific code soon.

We might actually make this bug more generic and use it for dividing up browser.js for each of the supported applications (Firefox, GeckoView, and Thunderbird). That do you think?

What do we have to discuss regarding the whiteboard entry?

Removing the entry.

Whiteboard: [webdriver:triage]
Priority: -- → P3
Summary: Ship remote/shared/MobileTabBrowser.jsm only on ANDROID builds → Extract application specific logic from browser.js in dedicated modules
You need to log in before you can comment on or make changes to this bug.