Skip to content

Conversation

@ashishkum-ms
Copy link
Contributor

Move the "deactivate an EditContext" step earlier in the HTMLElement.editContext replacement algorithm so deactivation steps (e.g., compositionend) run while the EditContext is still associated with its element

Closes #75

For normative changes, the following tasks have been completed:

@ashishkum-ms ashishkum-ms force-pushed the update-deactivate-timing-spec branch from b3f8b55 to 3a5f3e0 Compare September 3, 2025 08:51
@ashishkum-ms ashishkum-ms force-pushed the update-deactivate-timing-spec branch from 3a5f3e0 to cb7b93e Compare September 3, 2025 08:53
@ashishkum-ms ashishkum-ms force-pushed the update-deactivate-timing-spec branch from 3932cbc to d3043e0 Compare September 4, 2025 12:45
Copy link
Contributor

@dandclark dandclark left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think this is mostly ready, just one more stylistic comment.

Copy link
Contributor

@dandclark dandclark left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for getting this done!

@dandclark dandclark merged commit d98f84e into w3c:gh-pages Sep 5, 2025
2 of 3 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

The timing of "deactivate an EditContext" when HTMLElement.editContext is replaced with another one or null

2 participants