EventsDispatcher should retrieve browsing contexts via BrowsingContext.get
Categories
(Remote Protocol :: Agent, task, P3)
Tracking
(firefox139 fixed)
| Tracking | Status | |
|---|---|---|
| firefox139 | --- | fixed |
People
(Reporter: jdescottes, Assigned: jdescottes)
References
Details
(Whiteboard: [webdriver:m16])
Attachments
(1 file)
EventsDispatcher unnecessarily uses TabManager.getBrowsingContextById today. All the context ids found in events' contextInfo should be platform browsing context ids, and not TabManager UUIDs. Therefore we don't need the overhead of getBrowsingContextById. Also will unblock Bug 1761445
| Assignee | ||
Comment 1•1 year ago
|
||
All context ids handled by the events dispatcher are actual browsing context ids and not
TabManager UUIDs, there is no reason to use getBrowsingContextById here.
Updated•1 year ago
|
Comment 2•10 months ago
|
||
There is an r+ patch which didn't land and no activity in this bug for 2 weeks.
:jdescottes, could you have a look please?
If you still have some work to do, you can add an action "Plan Changes" in Phabricator.
For more information, please visit BugBot documentation.
Julian, can you please check why we didn't land this patch?
| Assignee | ||
Comment 4•10 months ago
|
||
Let's rebase and do a try push, I don't remember why this didn't land.
https://treeherder.mozilla.org/jobs?repo=try&revision=a8b06370eb2aa82bef10b6193665caf9e4600578
Try looks green I'll land this.
Comment 6•10 months ago
|
||
| bugherder | ||
| Assignee | ||
Updated•10 months ago
|
Description
•