[css-pseudo-4] painting of the cursor and the caret with highlight pseudos · Issue #4100 · w3c/csswg-drafts · GitHub
Skip to content
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

[css-pseudo-4] painting of the cursor and the caret with highlight pseudos #4100

Closed
frivoal opened this issue Jul 10, 2019 · 2 comments
Closed
Assignees
Labels
Closed Accepted by CSSWG Resolution Commenter Satisfied Commenter has indicated satisfaction with the resolution / edits. css-pseudo-4 Current Work

Comments

@frivoal
Copy link
Collaborator

frivoal commented Jul 10, 2019

https://drafts.csswg.org/css-pseudo-4/#highlight-styling says that highlight pseudos can take the caret-color and cursor properties, but https://drafts.csswg.org/css-pseudo-4/#highlight-painting doesn't say how they're rendered.

Possibilities:

  • the topmost one wins
  • the topmost non auto wins
@frivoal frivoal added the css-pseudo-4 Current Work label Jul 10, 2019
@frivoal frivoal self-assigned this Jul 10, 2019
@fantasai
Copy link
Collaborator

Related question: is there a use case for this and any implementation interest? Because if not I'm happy to defer this question and the feature entirely to L5. :)

@css-meeting-bot
Copy link
Member

The CSS Working Group just discussed [css-pseudo-4] painting of the cursor and the caret with highlight pseudos, and agreed to the following:

  • RESOLVED: drop caret-color and cursor
The full IRC log of that discussion <dael> Topic: [css-pseudo-4] painting of the cursor and the caret with highlight pseudos
<dael> github: https://github.com//issues/4100
<GameMaker> q+
<dael> fantasai: florian asked hwat happened with multi highlights and different caret values. Which one wins. top or top non-auto. Top most non-auto makes more sense I think but I don't know. Is anyone planning to impl these properties?
<castastrophe> Sorry, I need to drop
<dael> Rossen_: Regardless of plan to impl we should be able to define expected behavior. If top-most non-auto makes most sense we can resolve and when people impl if it's not the right choice we can discuss again then
<dael> florian: Alternative could be if no one thinks this is good to impl we could drop from list of elements that apply to this psedo element. These were added b/c not layout effecting. But if there's no interest we could drop them.
<dael> Rossen_: CHoices are drop it or top-most non-auto
<Rossen_> q?
<dael> GameMaker: I wasn't on the call but I recall reading notes about issues with this and grammar and auto-spell check b/c loading resources could be a security issue
<Rossen_> ack GameMaker
<dael> GameMaker: Maybe didn't understand discussion, but thinking that could be a reason to drop. In my impl I haven't looked at doing cursor or caret. Definitely would be more complicated to do. I'm in favor of just dropping cursor and caret
<tantek> +1 to dropping. seems to add complexity for theoretical reasons
<dael> Rossen_: Anyone want to keep those?
<dael> florian: Not a strong want but it seems security only applied to one of the two. Caret color won't load resources
<dael> fantasai: But if no one wants to impl and there's no strong usecase we should drop
<tantek> I'd be in favor of only reconsidering them if an implementor felt compelled to try implementing it (for whatever reason)
<dael> Rossen_: Objections to dropping caret-color and cursor?
<dael> RESOLVED: drop caret-color and cursor

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Closed Accepted by CSSWG Resolution Commenter Satisfied Commenter has indicated satisfaction with the resolution / edits. css-pseudo-4 Current Work
Projects
None yet
Development

No branches or pull requests

3 participants