1176950 - [e10s][TSF] nsTextStore shouldn't abandon locked content cache before dispatching events because they may be handled asynchronously in e10s mode

Status: RESOLVED FIXED

(Core :: Widget: Win32, defect)

Description

[Masayuki Nakano [:masayuki] (he/him)(JST, +0900)]

Currently, nsTextStore clears mLockedContent before dispatching events. However, in e10s mode, the content will receive the events asynchronously. So, from the view of content process, the document lock should be being kept.

When nsTextStore receiving a notification (except layout change), it should release the mLockedContent. In such timing, TabParent should finish preparing the content cache.

This may cause TIP being confused as content isn't modified by the sending events if it queries content synchronously.

Comment 1

[Masayuki Nakano [:masayuki] (he/him)(JST, +0900)]

Attachment: nsTextStore should keep storing locked content until NOTIFY_IME_OF_COMPOSITION_UPDATE is notified

After TextComposition dispatches a received event into the DOM tree, NOTIFY_IME_OF_COMPOSITION_UPDATE is notified. Therefore, nsTextStore can clear locked content which it's notified.

For asynchronous handling case (i.e., the event target is in a child process), nsTextStore should put off to forget the locked content. Then, nsTextStore can behave there is text content expected by TSF.

Comment 2

[Pulsebot]

https://hg.mozilla.org/integration/mozilla-inbound/rev/063a7521a10b

Comment 3

[Carsten Book [:Tomcat]]

https://hg.mozilla.org/mozilla-central/rev/063a7521a10b