Closed Bug 1218265 Opened 9 years ago Closed 3 years ago

drop support for multiple snap coordinates in 'scroll-snap-coordinate'

Categories

(Core :: Layout, task)

task
Not set
normal

Tracking

()

RESOLVED FIXED
Tracking Status
firefox44 --- affected

People

(Reporter: dbaron, Unassigned)

References

(Blocks 1 open bug)

Details

(Keywords: dev-doc-needed, site-compat)

The CSS Working Group just resolved to change 'scroll-snap-coordinate' so it will only support a single snap position (i.e., removing the comma-separated syntax with multiple positions). We should drop this support to match. (There may be another change coming to scroll-snap-coordinate's syntax shortly, though.)
Flags: needinfo?(roc)
'scroll-snap-coordinate' was dropped completely in the latest spec. versions together with 'scroll-snap-destination' in favor of new 'scroll-snap-margin-*', 'scroll-snap-padding-*' and 'scroll-snap-align'. David, I'm not sure whether it's better to do all these changes in one bug or whether to separate the removal and the implementations of the new properties up into separate bugs. So it would be great if you could clarify that. Sebastian
Flags: needinfo?(dbaron)
I think it's probably best to start with a metabug for updating the implementation to match the current spec, add existing bugs on the pieces as dependencies, but not file other dependencies until whoever works on that decide whether it needs to be split into multiple bugs.
Flags: needinfo?(dbaron)
(In reply to David Baron :dbaron: ⌚️UTC-7 from comment #2) > I think it's probably best to start with a metabug for updating the > implementation to match the current spec Good, for that we already have bug 1231777. > add existing bugs on the pieces as > dependencies, but not file other dependencies until whoever works on that > decide whether it needs to be split into multiple bugs. Sounds reasonable. Thanks for the feedback! Sebastian
Type: defect → task
Keywords: site-compat

This seems to be have been done as part of some other bug. Can we close that one?

Yes. Thanks!

Status: NEW → RESOLVED
Closed: 3 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.