Input event not fired on content editable

Confirmed Issue #12399539 • Assigned to Karan L.

Details

Author
Javan M.
Created
Jun 20, 2017
Privacy
This issue is public.
Found in
  • Microsoft Edge
Found in build #
15.15063
Reports
Reported by 1 person

Sign in to watch or report this issue.

Steps to reproduce

  1. Open the attached mutation-inspector.html file

  2. Place the cursor after the “a”

  3. Press Enter

Note that three separate collections of MutationRecords are dispatched:
Edge 15063

All other browsers dispatch one collection containing significantly different records:
Chrome, Safari, Firefox

–this repro below doesn’t repro anymore–

If the element’s contents are replaced in response to a mutation like this, Edge locks up and eventually reloads the page (not sure if it’s crashing, technically).
Steps to reproduce:

  1. Open the attached mutation-inspector.html file

  2. Check the “Render after each mutation” checkbox

  3. Place the cursor after the “a”

  4. Press Enter

The is a simplified representation of the mechanics of the Trix rich text editor, which monitors mutations and input events to update an internal document model, and then renders that model back to the contenteditable element as it changes. The issue is reproducible on https://trix-editor.org by clearing the editor’s contents, typing a character and then pressing enter.

Note: It appears this issue is no longer present in build 15.16215.

Edge 16215

I don’t see any relevant entries in the release notes so it’s unclear if it was fixed intentionally.

Thanks for your time and attention! ❤️

Attachments

Comments and activity

  • Changed Steps to Reproduce

    Changed Title from “Incorrect mutation records / record grouping when pressing return in a contenteditable element [crash possible]” to “Incorrect mutation records / record grouping when pressing return in a contenteditable element [crash possible]”

    Changed Steps to Reproduce

    Changed Steps to Reproduce

  • Microsoft Edge Team

    Changed Title from “Incorrect mutation records / record grouping when pressing return in a contenteditable element [crash possible]” to “Input event not fired on content editable”

    Changed Assigned To to “Grisha L.”

  • Moving to the text team, particularly Grisha to look into. The text team have been doing some awesome work and all of the above statements no longer repro. That said, we don’t seem to be firing an input event which we should be. Modifying the title and assigning to Grisha.

  • Good catch! The “input” event is fired when typing a character. Not fired when pressing enter.

  • Microsoft Edge Team

    Changed Steps to Reproduce

    Changed Status to “Confirmed”

    Changed Assigned To from “Grisha L.” to “Amit J.”

    Changed Steps to Reproduce

    Changed Steps to Reproduce

    Changed Assigned To from “Amit J.” to “Karan L.”

You need to sign in to your Microsoft account to add a comment.

Sign in