Hi there -

Given that this change is web observable, have you all done any compatibility testing or analysis to ensure sites aren't relying on the differences between engines here (hopefully not, but you know...)?

On 9/25/23 7:59 PM, 'Siye Liu' via blink-dev wrote:
Hi blink-dev,

We've been landing a change <https://chromium-review.googlesource.com/c/chromium/src/+/4878553>to enable new event ordering for beforeinput and compositionupdate during IME composition.

The previous event ordering for IME composition was:

keydown -> compositionstart -> *beforeinput -> compositionupdate* -> input -> keyup -> keydown -> *beforeinput -> compositionupdate* -> textInput -> input -> compositionend -> keyup.

The new ordering is:

keydown -> compositionstart -> *compositionupdate -> beforeinput* -> input -> keyup -> keydown -> *compositionupdate -> beforeinput* -> textInput -> input -> compositionend -> keyup.

This change aligns our event ordering with the behavior of Firefox and Safari, which fire the beforeinput event after the compositionupdate event.

The new event ordering is controlled by a runtime enabled feature flag that is set to stable status (enabled by default).
--
You received this message because you are subscribed to the Google Groups "blink-dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to blink-dev+unsubscr...@chromium.org. To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/bc3e3ab9-0740-4a4a-83f9-f95694f0127cn%40chromium.org <https://groups.google.com/a/chromium.org/d/msgid/blink-dev/bc3e3ab9-0740-4a4a-83f9-f95694f0127cn%40chromium.org?utm_medium=email&utm_source=footer>.

--
You received this message because you are subscribed to the Google Groups 
"blink-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to blink-dev+unsubscr...@chromium.org.
To view this discussion on the web visit 
https://groups.google.com/a/chromium.org/d/msgid/blink-dev/b56a3104-8f16-4d60-95ab-62b8705c4a7f%40chromium.org.

Reply via email to