[css-scroll-snap][cssom] Define interaction of ScrollIntoView options and scroll-snap · w3c/csswg-drafts#1708

(1 留言) (0 反應) (0 負責人)HTML (3,546 star) (545 fork)batch import

Closed Accepted by CSSWG ResolutionHelp WantedNeeds Editscssom-view-1

描述

Scroll Snap and CSSOM View currently conflict with each other: they both attempt to define the position of the element wrt the viewport when scrolled into view.

For sure, Scroll Snap should win when there's no arguments given to the API.

I also think that the positioning arguments should be dropped in favor of control with the scroll snap properties, unless there's a compelling reason why a JS API call needs a different value than is given declaratively in CSS. (Note, according to MDN, ScrollIntoViewOptions have only been implemented in Gecko.)

貢獻者指南

技術棧: html
領域: frontend
議題類型: research
難度: 5
預計時間: over 1 week
活動狀態: stale
清晰度: mostly clear
前置要求: CSS scroll snapCSSOM View specscrollIntoView API
新手友善度: 5
研究方向: Investigate the CSS Scroll Snap spec (css scroll snap 1) and CSSOM View spec to understand the conflicting definitions. Review the linked comment about Gecko's implementation of ScrollIntoViewOptions. Determine if scroll snap should take precedence over JS positioning arguments or if there are valid use cases for the JS API to override. Engage with maintainers for clarification on the preferred behavior.