Closed
Bug 1045413
Opened 10 years ago
Closed 9 years ago
PuppetWidget always requests IME selection and text change notifications
Categories
(Core :: DOM: Events, defect)
Tracking
()
RESOLVED
FIXED
Tracking | Status | |
---|---|---|
e10s | + | --- |
People
(Reporter: billm, Unassigned)
References
Details
The code is here:
http://mxr.mozilla.org/mozilla-central/source/widget/xpwidgets/PuppetWidget.cpp#567
The comment for these flags says they may be expensive if an HTML editor has focus:
http://mxr.mozilla.org/mozilla-central/source/widget/nsIWidget.h#206
I wonder if this is why typing emails in Gmail seems sluggish in e10s?
Reporter | ||
Updated•10 years ago
|
tracking-e10s:
--- → ?
Comment 1•10 years ago
|
||
Have you profiled gmail usage? Is it latency for keyboard events from parent to child + painting
which takes time or do we really do extra work?
Comment 2•10 years ago
|
||
While typing an email I see ~1.6% under PuppetWidget::NotifyIMEOfTextChange
Comment 3•10 years ago
|
||
Painting seems to take most of the time.
Updated•10 years ago
|
Comment 4•10 years ago
|
||
If we need to avoid, we need to support synchronous query content event support even on e10s. They are used for caching the content data in TabParent.
Anyway, text change performance should be improved. It's always enabled in TSF mode on Windows and on Android.
Comment 5•9 years ago
|
||
Is this still problem in the latest Nightly? I added a lot of improvements around this issue. I cannot say the demerit of enabling to notify IME of text changes is 0, but I feel current build is enough fast.
Updated•9 years ago
|
Flags: needinfo?(wmccloskey)
Reporter | ||
Comment 6•9 years ago
|
||
I don't see any difference in performance anymore.
Status: NEW → RESOLVED
Closed: 9 years ago
Flags: needinfo?(wmccloskey)
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•