Closed Bug 1282669 Opened 9 years ago Closed 9 years ago

Get rid of nsIMEUpdatePreference::DontNotifyChangesCausedByComposition()

Categories

(Core :: Widget, defect)

defect
Not set
normal

Tracking

()

RESOLVED FIXED
mozilla50
Tracking Status
firefox50 --- fixed

People

(Reporter: masayuki, Assigned: masayuki)

References

Details

(Keywords: inputmethod)

Attachments

(1 file)

Due to supporting e10s mode, DontNotifyChangesCausedByComposition() is worked well only with non-e10s cases (e.g., searchbar in chrome) because selection or text changes occurs asynchronously. I think that we can remove it and widget should ignore the notifications if it's actually not necessary.
I think that we can drop nsIMEUpdatePreference::DontNotifyChangesCausedByComposition(), i.e., nsIMEUpdatePreference::NOTIFY_CHANGES_CAUSED_BY_COMPOSITION because it's now used only by TSFTextStore but TSFTextStore ignores if SelectionChangeDataBase::mCausedByComposition or TextChangeDataBase::mCausedOnlyByComposition is true (for supporting async changes in e10s mode). So, only issue is, dropping the flag might cause increasing computing TextChangeData cost during composition in TSF mode. However, now, it's already enough fast and even if it'd cause performance regression, we could add a hack with TextComposition's offset information. Therefore, we don't need to worry about the performance regression so seriously. Review commit: https://reviewboard.mozilla.org/r/61000/diff/#index_header See other reviews: https://reviewboard.mozilla.org/r/61000/
Attachment #8765814 - Flags: review?(m_kato)
Comment on attachment 8765814 [details] Bug 1282669 Get rid of nsIMEUpdatePreference::DontNotifyChangesCausedByComposition() https://reviewboard.mozilla.org/r/61000/#review58032
Attachment #8765814 - Flags: review?(m_kato) → review+
Pushed by masayuki@d-toybox.com: https://hg.mozilla.org/integration/autoland/rev/032a49223156 Get rid of nsIMEUpdatePreference::DontNotifyChangesCausedByComposition() r=m_kato
Status: ASSIGNED → RESOLVED
Closed: 9 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla50
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: