-
Notifications
You must be signed in to change notification settings - Fork 6
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
The timing of "deactivate an EditContext" when HTMLElement.editContext
is replaced with another one or null
#75
Comments
It is a good point that firing If we make this change though, I would propose that step 6 be moved even earlier, before step 2.3. After 2.3 things are in an inconsistent state because we've changed the EditContext's associated element but not yet updated the Element's [[EditContext]] internal slot, so we shouldn't fire |
Yeah, sounds reasonable! |
We resolved during today's Editing WG call to do this reordering.
|
https://w3c.github.io/edit-context/#extensions-to-the-htmlelement-interface
In the list:
I think that the Step.6 should be between Step 4.1 and 4.2 because it's odd and may be error prune if it happens after disassociated from an element.
The text was updated successfully, but these errors were encountered: