Skip to content

Clarify how CompositionEvents should be initialized #129

@ltenmoz

Description

@ltenmoz

Currently the language around firing compositionstart/end events is just:

Fire an event named compositionstart/compositionend at editContext using CompositionEvent.

But this doesn't make it clear how the view and data attributes should be initialized. There is the table in the UI Events spec, but that seems to only apply to non-EditContext composition events on elements. Probably the EditContext spec should be explicit about this.

It's also not clear if these events should bubble or not. Currently Chrome has them not bubble, but composition events for <input>/contenteditable do bubble, so maybe it would be best to be consistent?

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions