Skip to content

Conversation

@dinukadesilva
Copy link

@lovasoa
Copy link
Owner

lovasoa commented Mar 31, 2018

thank you for the PR

@lovasoa
Copy link
Owner

lovasoa commented Mar 31, 2018

but I don't think exposing the state as a list of boolean properties is a good idea

@lovasoa
Copy link
Owner

lovasoa commented Mar 31, 2018

what should the user expect if he sets several boolean state options to true?

@dinukadesilva
Copy link
Author

It is according to the priority sequence mentioned in https://w3c.github.io/editing/contentEditable.html#h-contenteditable. That's why these have been enclosed in separate if clauses.

@dinukadesilva
Copy link
Author

@lovasoa Any updates regarding this pull request

@lovasoa lovasoa changed the title gh-84: Addition additional states of contenteditable #84: Addition additional states of contenteditable Aug 5, 2018
@lewisf
Copy link

lewisf commented Nov 13, 2019

any updates on this? can i help with any changes to move this along?

@lewisf lewisf mentioned this pull request Nov 13, 2019
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.

Additional states "events", "caret", "typing", "plaintext-only"

3 participants