зеркало из https://github.com/mozilla/gecko-dev.git
111854b5a5
* TabObserver is rather an helper class of Targets rather than RemoteAgent. Targets is the class which holds all the targets and reports about their creation and destructor. It feels legitimate to have it directly integrate with TabObserver. * To better sort of the files. i.e. avoid having "random files" in /remote/ I'm renaming and moving TabObserver according to its usage. * We were emitting "connect" and "disconnect" event when a target was created or destroyed. But this is misleading as there is no connection to anything being made. Only later, a CDP client might connect to a target HTTP endpoint and initiate a connection. These events are making this hard to understand that the connection actually happens when Target.handle is called. Differential Revision: https://phabricator.services.mozilla.com/D37043 --HG-- rename : remote/WindowManager.jsm => remote/targets/TabObserver.jsm extra : moz-landing-system : lando |
||
|---|---|---|
| .. | ||
| browser | ||
| unit | ||
| demo.js | ||
| moz.build | ||
| puppeteer-demo.js | ||