Add an async version of createContentWindow and use it wherever possible
Categories
(GeckoView Graveyard :: Sandboxing, task, P3)
Tracking
(firefox127 fixed)
Tracking | Status | |
---|---|---|
firefox127 | --- | fixed |
People
(Reporter: agi, Assigned: m_kato)
References
(Blocks 2 open bugs)
Details
(Whiteboard: [fission:android])
Attachments
(1 file, 2 obsolete files)
The GeckoView implementation of createContentWindow
spins the event loop to respond synchronously, but its return value is actually put inside a promise for some callers. We should add an async version of it (e.g. createContentWindowAsync
) and call it wherever possible to avoid spinning the event loop unnecessarily.
Comment 1•3 years ago
|
||
This problem will be made worse with Fission.
This fix won't require any Fenix changes.
Comment 2•3 years ago
|
||
Moving Android Fission bugs to the new GeckoView::Sandboxing component.
Assignee | ||
Updated•2 years ago
|
Assignee | ||
Comment 3•2 years ago
|
||
GeckoView's createContentWindow is implemented by JavaScript and Java. To use
callback, we need to access from JavaScript.
Assignee | ||
Comment 4•2 years ago
|
||
Depends on D197131
Assignee | ||
Comment 5•2 years ago
|
||
Depends on D197132
Comment 6•2 years ago
|
||
The following patch is waiting for review from an inactive reviewer:
ID | Title | Author | Reviewer Status |
---|---|---|---|
D197131 | Bug 1777509 - Part 1. Make nsIBrowsingContextReadyCallback scriptable. | m_kato | nika: Back Jan 2, 2024 |
:m_kato, could you please find another reviewer?
For more information, please visit BugBot documentation.
Assignee | ||
Updated•2 years ago
|
Comment 7•2 years ago
|
||
(In reply to Chris Peterson [:cpeterson] from comment #1)
This problem will be made worse with Fission.
Agi said Fission will make this problem worse, so I will track this bug for Android Fission.
Updated•2 years ago
|
Updated•1 year ago
|
Updated•1 year ago
|
Comment 9•1 year ago
|
||
bugherder |
Updated•1 year ago
|
Updated•1 year ago
|
Description
•