Skip to content

Commit 9955710

Browse files
committed
[css-snappoints] Adding issue for finding a better term than snap alignment container
1 parent 5ffc2db commit 9955710

2 files changed

Lines changed: 5 additions & 1 deletion

File tree

css-snappoints/Overview.bs

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -186,6 +186,7 @@ Ignored Terms: scroll-snap-positions-*, containing block chain
186186
<dt><dfn export>snap alignment container</dfn>
187187
<dd>
188188
A scroll container's snap alignment container is the rectangle obtained by reducing its visual viewport by its 'scroll-snap-padding'.
189+
<p class="issue">Better name for this concept?</p>
189190

190191
<dt><dfn lt="scroll snap area" local-lt="snap area" export>snap area</dfn>
191192
<dd>

css-snappoints/Overview.html

Lines changed: 4 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -331,7 +331,9 @@ <h2 class="heading settled" data-level="4" id="definitions"><span class="secno">
331331
<dt><dfn data-dfn-type="dfn" data-export="" id="scroll-container">scroll container<a class="self-link" href="#scroll-container"></a></dfn>
332332
<dd> An element which provides a scrolling user interface as described in <a data-link-type="biblio" href="#biblio-css21">[CSS21]</a>, particularly in the section on overflow.
333333
<dt><dfn data-dfn-type="dfn" data-export="" id="snap-alignment-container">snap alignment container<a class="self-link" href="#snap-alignment-container"></a></dfn>
334-
<dd> A scroll container’s snap alignment container is the rectangle obtained by reducing its visual viewport by its <a class="property" data-link-type="propdesc" href="#propdef-scroll-snap-padding">scroll-snap-padding</a>.
334+
<dd>
335+
A scroll container’s snap alignment container is the rectangle obtained by reducing its visual viewport by its <a class="property" data-link-type="propdesc" href="#propdef-scroll-snap-padding">scroll-snap-padding</a>.
336+
<p class="issue" id="issue-1b6eda6b"><a class="self-link" href="#issue-1b6eda6b"></a>Better name for this concept?</p>
335337
<dt><dfn data-dfn-type="dfn" data-export="" data-local-lt="snap area" data-lt="scroll snap area" id="scroll-snap-area">snap area<a class="self-link" href="#scroll-snap-area"></a></dfn>
336338
<dd> An element’s snap area is the rectangle obtained by expanding its border box by its <a class="property" data-link-type="propdesc" href="#propdef-scroll-snap-area">scroll-snap-area</a>.
337339
<dt><dfn data-dfn-type="dfn" data-export="" data-local-lt="snap position" data-lt="scroll snap position" id="scroll-snap-position">snap position<a class="self-link" href="#scroll-snap-position"></a></dfn>
@@ -724,6 +726,7 @@ <h2 class="no-num heading settled" id="property-index"><span class="content">Pro
724726
<h2 class="no-num heading settled" id="issues-index"><span class="content">Issues Index</span><a class="self-link" href="#issues-index"></a></h2>
725727
<div style="counter-reset:issue">
726728
<div class="issue"> <b>This spec is currently undergoing major changes in line with the resolutions in <a href="https://lists.w3.org/Archives/Public/www-style/2015Dec/0048.html">https://lists.w3.org/Archives/Public/www-style/2015Dec/0048.html</a>. During this process it is not safe to assume that the current form will be representative of what it will look like in the future. After the work in process is completed, it will closely resemble <a href="https://drafts.csswg.org/css-scroll-snap/">this proposal</a>.</b> <a href="#issue-752e30a5"></a></div>
729+
<div class="issue">Better name for this concept?<a href="#issue-1b6eda6b"></a></div>
727730
<div class="issue"> <a href="https://lists.w3.org/Archives/Public/www-style/2015Nov/0328.html">Open issue</a> on whether to enhance the scroll-snap-type property for specifying the axis or adding a second property. We have <a href="https://lists.w3.org/Archives/Public/www-style/2015Dec/0048.html">resolved</a> that this functionality be added once the issue is resolved. <a href="#issue-7e0cf181"></a></div>
728731
<div class="issue"> Should this be x/y axes, or inline/block? Starting with x/y axes for consistency with padding/area, otherwise a writing mode change would result in a axis mismatch (since padding is physical by default). <a href="#issue-f7391e31"></a></div>
729732
</div>

0 commit comments

Comments
 (0)