Bug 189265 - Rename scroll-snap-margin to scroll-margin, and have it apply when scrolling to anchors
Summary: Rename scroll-snap-margin to scroll-margin, and have it apply when scrolling ...
Status: RESOLVED FIXED
Alias: None
Product: WebKit
Classification: Unclassified
Component: CSS (show other bugs)
Version: Safari Technology Preview
Hardware: All All
: P2 Normal
Assignee: Simon Fraser (smfr)
URL:
Keywords: BrowserCompat, InRadar, WebExposed
: 208110 (view as bug list)
Depends on: 218075 218076
Blocks: 218115
  Show dependency treegraph
 
Reported: 2018-09-04 11:36 PDT by Michał Gołębiowski-Owczarek
Modified: 2020-10-29 13:06 PDT (History)
16 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Michał Gołębiowski-Owczarek 2018-09-04 11:36:41 PDT
It looks that the CSS Scroll Snap spec has changed and what was named `scroll-snap-margin` is now named `scroll-margin`. The just released Chrome 69 supports only `scroll-margin`.
Comment 1 Mikaela Young 2019-11-04 12:36:23 PST
Scroll margin should also still be applied when snapping is not turned on or applied to the element, allowing it's use with anchor links.

See https://drafts.csswg.org/css-scroll-snap-1/#propdef-scroll-margin.
Comment 2 Radar WebKit Bug Importer 2019-11-04 12:43:17 PST
<rdar://problem/56875889>
Comment 3 Simon Fraser (smfr) 2020-04-30 11:38:20 PDT
*** Bug 208110 has been marked as a duplicate of this bug. ***
Comment 4 dakur 2020-05-21 07:26:55 PDT
Any news on this please? It would save a lot of pain when linking to URLs with hash as current hack with negative margin-top & positive padding-top is not reliable as it brings new issues with overlaying elements.
Comment 5 Ben Frain 2020-06-23 08:22:37 PDT
Pretty standard stuff this. Any ETA on when we might see it in WebKit?
Comment 6 netleon6@gmail.com 2020-10-05 00:28:31 PDT
scroll-margin & scroll-snap-margin not working in Safari

Please add this, make us easy to access the web
don't make it partial on some browsers it will work on some don't
Comment 7 netleon6@gmail.com 2020-10-05 00:29:07 PDT
(In reply to Ben Frain from comment #5)
> Pretty standard stuff this. Any ETA on when we might see it in WebKit?

Do you think they reading this!!
Comment 8 Simon Fraser (smfr) 2020-10-05 10:52:17 PDT
They is
Comment 9 Emily 2020-10-21 06:57:02 PDT
Also interested in the resolution of this bug in the near future, so that we can get rid of ad-hoc JS code. Thanks!
Comment 10 Martin Robinson 2020-10-22 03:46:13 PDT
I've decided to divide this work into at least two dependent bugs.
Comment 11 dakur 2020-10-22 06:56:13 PDT
Thank you! Just for tracking purposes, these two bugs are follow-ups from this one:
- https://bugs.webkit.org/show_bug.cgi?id=218075
- https://bugs.webkit.org/show_bug.cgi?id=218076
Comment 12 Martin Robinson 2020-10-29 05:20:58 PDT
Both dependent bugs have been closed, so I think this can be closed as well.