-
Notifications
You must be signed in to change notification settings - Fork 707
[css-scroll-snap-1] Unclear what mapping the 4-value longhands use #1050
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
Comments
We specify this:
|
Sorry, this doesn't address my concern at all, first the link to 'border-image-outset' is completely irrelevant as it has neither physical or logical longhands, nor any way to set the values in logical directions (afaict). Second, the link to 'margin' in css2.1 has no reference to or mention of logical properties. The concern here came up during TAG review, scroll-snap specifies a shorthand, and both physical and logical longhands, but has absolutely no information that explains how the shorthand maps to the longhands, and the links given don't help. While I could make an educated guess, others couldn't. At the least, a brief sentence explaining that the shorthand sets all the longhands, in the manner described by css-logical §3.2 (or a better link) would be helpful. I get that this is probably obvious to the editors, but it's not obvious to a casual reader (which is the real issue). |
OK, I checked in some changes. @plinss could you review? |
It's an improvement (and I accept that you gave me exactly what I asked for), but I still think it could be better.
Reading css-scroll-snap without having css-logical fully swapped in, can lead a reader to think that a declaration of Perhaps a paragraph in each of the physical and flow-realtive longhand descriptions in Appendix A stating that the physical longhands are only set by the shorthand when the 'logical' is not present and the flow-relative longhands are only set when the 'logical' keyword is present... |
The |
Ok, so if css-logical isn't stable enough then I accept that it doesn't make sense to be overly specific in this spec. Perhaps an additional sentence in the beginning of Appendix A indicating that the mapping between the shorthand and longhand properties is also determined by css-logical? With that I'd be satisfied. (I'm also not sure that the shorthand setting all longhands vs just the physical/logical longhands is irrelevant, while the end result may not be observable in layout/scroll behavior, it will be observable in the CSSOM.) |
Ok, added 393d993 |
Commits on Jun 17, 2017 Convert period to semicolon per lawyers demands. w3c/csswg-drafts#1305 w3c/csswg-drafts@0a7ab91674e5bd7882ae527fe4749 e81cf1be236 Commits on Jun 20, 2017 Update Changes list. w3c/csswg-drafts@617e94fb07ce681680bfbac61f0ac ec7c6599f3b Rearrange prose to be clearer about value mapping to longhands, link to css-logical. Fixes w3c/csswg-drafts#1050 . w3c/csswg-drafts@38caa2ee20ca9833a1ad401b03c96 debcac0cc21 Commits on Jun 22, 2017 add that shorthand interactions are also governed by css-logical w3c/csswg-drafts@393d993047493a042491806239cea 6fff215f060
Works for me, thanks! |
scroll-padding and scroll-snap-margin shorthands are unclear as to which longhand properties are set (specifically physical or logical).
My guess is that the intent is the shorthand follows the standard TRBL pattern, and then physical sides are mapped to logical longhands based on writing mode, but this is not clear from reading the spec.
The text was updated successfully, but these errors were encountered: