Skip to content

[css-scroll-snap] snap points on pseudo elements #488

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

Closed
frivoal opened this issue Sep 15, 2016 · 3 comments
Closed

[css-scroll-snap] snap points on pseudo elements #488

frivoal opened this issue Sep 15, 2016 · 3 comments
Assignees
Labels
Closed Rejected as Wontfix by CSSWG Resolution Commenter Satisfied Commenter has indicated satisfaction with the resolution / edits. css-scroll-snap-1 Current Work

Comments

@frivoal
Copy link
Collaborator

frivoal commented Sep 15, 2016

In http://www.w3.org/mid/C65090CE-632C-4606-93A9-80F358A15510@rivoal.net, @tabatkins and I argued about snap points and pseudo elements. This was not resolved.

but I'd also be in favor of making it apply to all pseudo elements. As long as something has a box, we should have all we need to make things work.

Yeah, but it has to be tree-abiding, or else it's unpredictable how
many
snap-points it generates. This rules out ::first-letter and
::first-line, as well as all the highlight pseudos like
::spelling-error. This is the same reasoning that rules out
background-image and friends - it's unpredictable how many boxes the
pseudo-element will generate, as it depends intimately on the markup
it's applying to, and so we avoid any property that depends on or
visually exposes the number of boxes.

I'm not sure I follow. While these pseudos do weird things to the tree
(making it no longer a tree), how do they create more than one box? Or do
you mean the boxes generated by their children? Why would that matter
for a snappoint?

Also we do apply background image to non tree-abiding pseudos:
http://jsbin.com/nowose/edit?html,css,output

I mean, yes, the non tree abiding pseudos are weird in general, and
there's all sorts of issues with them, but could you clarify a bit
what causes problems with regards to snap-points?

@frivoal frivoal added the css-scroll-snap-1 Current Work label Sep 15, 2016
@frivoal frivoal self-assigned this Sep 15, 2016
@fantasai
Copy link
Collaborator

The reason we don't want to do this is because it is additional implementation and testing work for no clear use case. If at some point we introduce a pseudo-element that clearly needs to support scroll-snapping or there is a demand from the authoring community to add scroll-snapping to an existing pseudo-element, then we can add scroll-snapping to that specific pseudo-element.

We don't even blanket-whitelist backgrounds. We are not going to blanket-whitelist scroll-snapping.

@fantasai
Copy link
Collaborator

@frivoal
Copy link
Collaborator Author

frivoal commented Sep 20, 2016

Didn't remember that we had a resolution for this, sorry.
For the record, I'm OK with the conclusion.

@frivoal frivoal added the Commenter Satisfied Commenter has indicated satisfaction with the resolution / edits. label Sep 20, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Closed Rejected as Wontfix by CSSWG Resolution Commenter Satisfied Commenter has indicated satisfaction with the resolution / edits. css-scroll-snap-1 Current Work
Projects
None yet
Development

No branches or pull requests

2 participants