Closed Bug 962901 Opened 10 years ago Closed 4 years ago

Query content event via CPOW for e10s IME

Categories

(Core :: DOM: Events, defect)

Product:
Core
Component:
DOM: Events
Platform:
x86
Windows 8.1
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

()

Status:
RESOLVED WONTFIX
Tracking Flags:
Tracking Status
e10s - ---

People

(Reporter: m_kato, Assigned: m_kato)

References

Details

If TabParent's cahce for IME isn't hit, we should query NS_QUERY_* to content process for e10s.
- QueryContent.jsm for content process.
- TabParent uses nsFrameManager::SendSyncMessage and decode js object? or use js?
Blocks: e10s-ime
Move old M2's low-priority bugs to M6 milestone.
tracking-e10s: + → m6+
Hey Makoto, would you consider this bug still valid and if so, should it block e10s aurora uplift?
Flags: needinfo?(m_kato)
(In reply to Jim Mathies [:jimm] from comment #3)
> Hey Makoto, would you consider this bug still valid and if so, should it
> block e10s aurora uplift?

Sorry for delay.

Now, most NS_QUERY_* events support remote.  To support IME on e10s, some values are already cached from content process.  So this issue is a fallback if cache isn't hit.

I don't think this issue isn't block for e10s.
Flags: needinfo?(m_kato)
Thanks for the update. Removing milestone 6 tracking.
tracking-e10s: m6+ → -

CPOWs are being removed.

Status: NEW → RESOLVED
Closed: 4 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.