Closed
Bug 1524977
Opened 6 years ago
Closed 6 years ago
Use RemoteFrameChild if present in nsFocusManager::GetNextTabbableContent()
Categories
(Core :: DOM: Core & HTML, enhancement, P2)
Core
DOM: Core & HTML
Tracking
()
Tracking | Status | |
---|---|---|
firefox67 | --- | fixed |
People
(Reporter: hsivonen, Assigned: hsivonen)
References
Details
(Whiteboard: [fission-event-m1])
Attachments
(1 file)
(deleted),
text/x-phabricator-request
|
Details |
When focus traversal moves into an iframe in nsFocusManager::GetNextTabbableContent, in addition to checking if the nsIContent* being iterated to is associated with a TabParent, check whether it is associated with RemoteFrameChild. If it has a RemoteFrameChild, call NavigateByKey() on the RemoteFrameChild. (Assumption: RemoteFrameChild will have such a method that will bounce an IPC message to the chrome process and have the chrome process call NavigateByKey() on the TabParent associated with the RemoteFrameParent.)
Updated•6 years ago
|
Priority: -- → P2
Updated•6 years ago
|
Whiteboard: [fission-event-m1]
Updated•6 years ago
|
Fission Milestone: --- → M2
Assignee | ||
Comment 1•6 years ago
|
||
Assignee | ||
Updated•6 years ago
|
Assignee: nobody → hsivonen
Status: NEW → ASSIGNED
Pushed by hsivonen@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/ed8a0908ddf0
Use RemoteFrameChild if present in nsFocusManager::GetNextTabbableContent(). r=nika
Comment 3•6 years ago
|
||
bugherder |
Status: ASSIGNED → RESOLVED
Closed: 6 years ago
status-firefox67:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → mozilla67
You need to log in
before you can comment on or make changes to this bug.
Description
•