[css-highlight-api] Should ::highlights be printed?
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 25/100
- Issue type
- Documentation
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- css
- Domain
- documentation
Research direction
Start by reviewing the CSS Highlight API specification and its treatment of ::selection and ::target-text. Resolve whether ::highlight styles should appear in printed documents, considering semantic highlights versus find-on-page or spellcheck use cases, then clarify the decision in the spec.
Written by the indexing model from the issue text.
Description
Highlight pseudos are currently not printed, at least in the Chromium implementation.
Considering other pseudos like ::selection and ::target-text, it makes sense for these not to show up on printed documents. But for ::highlight it's less clear. Highlights used for emphasizing parts of the text might be appropriate to print. In some applications highlights could convey specific semantic value, e.g. a language-teaching application might use differently-colored highlights to demonstrate which parts of a sentence are verbs vs adverbs vs adjectives, etc. The user would likely expect these highlights to be printed.
On the other hand, highlights used for custom find-on-page or spellcheck probably shouldn't be printed.
Whatever we decide, we should probably add some clarity about this to the spec.
Thanks @mrego for raising this point.
- Dominant language
- Bikeshed
- Stars
- 4.9k
- Forks
- 816
- Avg merge
- 2d 18h
- Merged PRs (30d)
- 24
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from w3c/csswg-drafts
-
Agenda+ css-sizing-4 css-values-5
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
w3c/csswg-drafts#14502 · 1 reaction ·
-
css-values-5 editorial Needs Edits
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
w3c/csswg-drafts#14498 · 2 comments ·
-
css-overflow-4 topic: line-clamp
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
w3c/csswg-drafts#14485 · 1 comment ·
-
Administrative Tracker css-values-4
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
w3c/csswg-drafts#14482 · 4 comments · 1 reaction ·
-
css-values-5 Needs Edits
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
w3c/csswg-drafts#14466 ·
All issues in w3c/csswg-drafts
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
bancolombia/sentinel#22 ·
-
test md OpenCI
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
-
optimization optimization:agents-md-curator
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
githubnext/gh-aw-cao#13143 ·
-
Difficulty 1/5 Under an hour Newbie friendliness 94/100
objectionary/hone-maven-plugin#1061 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
redhat-developer/rhdh-plugins#4887 · 2 comments ·