[css-ui-4] Clarify the applicability of the caret-* properties #11373
Conversation
1b0e26b to
669d7a1
Compare
schenney-chromium
left a comment
There was a problem hiding this comment.
Thanks Florian. It's a significant improvement and will help me in moving the implementation forward.
aef81ff to
c5f67d6
Compare
css-ui-4/Overview.bs
Outdated
| The 'caret-color', 'caret-animation', and 'caret-shape' properties | ||
| give the author some amount of control over the appearance of the [=caret=]. | ||
|
|
||
| Elements are considered to <dfn>accept input</dfn> |
There was a problem hiding this comment.
In order to respect #5303 (comment), text may also be considered to accept input and then these properties should apply to it.
<!DOCTYPE html>
<div contenteditable>
<span style="display: contents; caret-color: magenta">aaaaaaa</span>
</div>
emilio
left a comment
There was a problem hiding this comment.
"Accept input" is really broad (all elements accept pointer input or so, right?). Probably "Accept text input" or "accept keyboard input"?
|
For all of the caret-* properties, could we also add something like "dynamic changes must be applied no later than the next blink cycle of the caret" or similar? That leaves UA free to implement the blinking -> non-blinking behavior in the most convenient manner (e.g. by letting a timer expire). |
|
Can we move this forward? @frivoal would you like me to take it over to incorporate the improvements suggested by Oriol, Emilio and myself? |
Co-authored-by: Emilio Cobos Álvarez <emilio@crisal.io>
Co-authored-by: Oriol Brufau <obrufau@igalia.com>
|
Sorry, this had fallen off my radar. I've added the changes requested by @Loirooriol and @emilio On the other hand, this seems like a separate topic:
@schenney-chromium could you open a separate issue for that? |
|
Thanks Florian. Yes, I'll create an issue for the updating of properties and get a PR up for it. |
See #11335