Re: [editing] Definition of "Invisible elements" is vague (#68)

> I'm sorry for the current situation, but let's forget this for now. At least in CE=events (and hopefully more if backward compat is ok) UA sets the caret to anywhere JS specifies.

Ok, not really knowing what's going on in a browser, it's not really clear to me why the caret will be drawn correctly every time with the new code. In the old code, it seems that there are certain places where the caret line is being drawn somewhere slightly different, and it doesn't blink while it's there. That's one of the kinds of things we want to avoid. The second, as you mention, that the caret/selection will not let itself be placed in certain places.

So the second is solved, but the first one? For that, I thought it would be the simplest to give you a list of places where the caret needs to be drawable (incl. blinking), but if say that doesn't help you, then we can remove it as well. How can we then ensure that if a specific browser does what Chrome does with the current setup, that we can file a bug because it doesn't draw the caret when it should?

I am fine with JS being responsible for not putting carets where they aren't visible and tweaking the DOM if necessary to make them visible.



---
Reply to this email directly or view it on GitHub:
https://github.com/w3c/editing/issues/68#issuecomment-132188979