Closed
Bug 1535537
Opened 6 years ago
Closed 6 years ago
Maintain information about focused TabParent on chrome main thread independently of APZ
Categories
(Core :: DOM: Content Processes, defect, P1)
Core
DOM: Content Processes
Tracking
()
RESOLVED
FIXED
mozilla68
| Tracking | Status | |
|---|---|---|
| firefox68 | --- | fixed |
People
(Reporter: hsivonen, Assigned: hsivonen)
References
Details
(Whiteboard: [fission-event-m1])
Attachments
(1 file)
|
(deleted),
text/x-phabricator-request
|
Details |
IME code needs to react to changes in which TabParent has focus. Getting this information from APZ makes an additional bounce via the GPU process (when the GPU process is in use), which potentially changes the relative order of focus changes relative to content processes sending IME notifications.
Since focus management notifications bounce via the chrome main thread anyway, let's listen to them there and make the chrome main thread keep track of which TabParent has focus and notify IME code whenever a TabParent loses focus.
|
Assignee | |
Comment 1•6 years ago
|
||
Pushed by hsivonen@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/dbe5292cac33
Maintain information about focused TabParent on chrome main thread independently of APZ. r=nika
|
||
Updated•6 years ago
|
Priority: -- → P1
|
||
Comment 3•6 years ago
|
||
| bugherder | ||
Status: ASSIGNED → RESOLVED
Closed: 6 years ago
status-firefox68:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → mozilla68
You need to log in
before you can comment on or make changes to this bug.
Description
•