Closed
Bug 1285420
Opened 8 years ago
Closed 8 years ago
Handle eQueryContentState for remote targets
Categories
(Core :: DOM: UI Events & Focus Handling, defect, P3)
Tracking
()
RESOLVED
WONTFIX
Tracking | Status | |
---|---|---|
firefox50 | --- | affected |
People
(Reporter: reuben, Unassigned)
References
Details
EventStateManager::HandleQueryContentEvent does not handle eQueryContentState for remote targets.
Reporter | ||
Comment 2•8 years ago
|
||
This is currently breaking Mac OS X Services integration. It looks like an alternative solution is being worked on in bug 1261299, which will make these bugs not urgent at all, and possibly a WONTFIX.
Flags: needinfo?(reuben.bmo)
Updated•8 years ago
|
Flags: needinfo?(jimmyw22)
Priority: -- → P3
Comment 3•8 years ago
|
||
Bug 1261299 makes Mac OS X Services integration work again by caching the current selection (chrome/ content process) because the services menu requires synchronous access to the current content selection. I'm caching it on the nsClipboard for macOS only. This makes this low priority or WONTFIX. eQueryContentState still does not work in e10s. If someone needed the same functionality we would need to cache the content selection on EventStateManager.cpp and make it available to Linux, OSX, Windows. We should also remove the current code for eQueryContentState because you can't dispatch a widget event to content in e10s like that.
Status: NEW → RESOLVED
Closed: 8 years ago
Flags: needinfo?(jimmyw22)
Resolution: --- → WONTFIX
Assignee | ||
Updated•5 years ago
|
Component: Event Handling → User events and focus handling
You need to log in
before you can comment on or make changes to this bug.
Description
•