Meeting minutes
zoom meeting link - https://us02web.zoom.us/postattendee?id=2
alexkeng: is doing presentation for EditContextAPI
EditContext explainer for reference - https://github.com/w3c/editing/blob/gh-pages/docs/EditContext/explainer.md
<smaug> Hmm, https://w3c.github.io/editing/docs/EditContext/explainer.html doesn't have attachEditContext
@smaug - apologies, we'll need to update it to reflect on new changes
whsieh: how does it interact with CE?
whsieh: what if it's attached to CE=true?
BoCupp: we need to think through CE=true
Biggest thing from last year is ability to attach editcontext to multiple elements
it allows us to leverage some of CE functionality e.g. spellcheck, caret, etc
essentially, attaching to CE let's us extract undesired side effects from CE.
whsieh: sounds like CE -disabled. As I recall there was an integration between CE-disabled it and Editcontext
BoCupp: they don't overlap. But we are still figuring out the details.
<Zakim> jamesn, you wanted to ask how we communicate to accessibility APIs that editing is available
whsieh: we need to be precise with how it works with other components
jamesn: can we have some Accessibility samples? Don't think we need anything new but if we do ARIA could help.
BoCupp: yep
we'll keep that in mind
@Johanees - looks similar to CE but CE-disabled seems to be about UI
Johannes: is using native selection or not a binary decision or can it be used interchangeably.
BoCupp: similar to CE-caret but it holds more state. We also want to have a separate view and be able to describe all text formatting information that EditContext receives. Agree that we need more precision of what is in/out when we attach to CE.
alexkeng to second question about native selection.
alexkeng: that should be possible
BoCupp: normally, a CE is using native selection. I think, I heard how do you move from one CE into another and finding correct position. We talked about possibility that the identity of editcontext and using dom order to figure out the next selection position. We could use something like associating different elements to be part of the same editcontext group.
ACTION- update the explainer with new behaviors added