Alexandre Poirot 111854b5a5 Bug 1563689 - Revamp how targets are watched and reported. r=remote-protocol-reviewers,ato,jdescottes ... * 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		2019-07-18 12:30:10 +00:00
..
browser	Bug 1563689 - Revamp how targets are watched and reported. r=remote-protocol-reviewers,ato,jdescottes	2019-07-18 12:30:10 +00:00
unit	Bug 1563692 - Move all CDP's JSON packet handling to Connection. r=remote-protocol-reviewers,jdescottes,ato	2019-07-11 17:45:29 +00:00
demo.js	Bug 1553103 - Document the node test script using chrome-remote-inteface. r=jdescottes	2019-06-18 22:05:56 +00:00
moz.build	bug 1523104: remote: add browser mochitest to test the agent via chrome-remote-interface; r=ato	2019-03-08 16:26:39 +00:00
puppeteer-demo.js	Bug 1561435 - Format remote/, a=automatic-formatting	2019-07-05 10:56:48 +02:00