Skip to content

Commit 9e92571

Browse files
committed
[css-snappoints] Removing issue regarding fragmentation per f2f resolution https://log.csswg.org/irc.w3.org/css/2015-10-25/#e613119
1 parent 62ff041 commit 9e92571

2 files changed

Lines changed: 0 additions & 6 deletions

File tree

css-snappoints/Overview.html

Lines changed: 0 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -342,7 +342,6 @@ <h2 class="heading settled" data-level="5" id="scroll-snap-destination"><span cl
342342
<h2 class="heading settled" data-level="6" id="scroll-snap-coordinate"><span class="secno">6. </span><span class="content">Scroll Snap Coordinate: the <a class="property" data-link-type="propdesc" href="#propdef-scroll-snap-coordinate">scroll-snap-coordinate</a> property</span><a class="self-link" href="#scroll-snap-coordinate"></a></h2>
343343
<p>The <a class="property" data-link-type="propdesc" href="#propdef-scroll-snap-coordinate">scroll-snap-coordinate</a> property is used to define the x and y coordinate within the element
344344
which will align with the nearest ancestor <a data-link-type="dfn" href="#scroll-container">scroll container’s</a> snap-destination for the respective axis. In the case that the element has been transformed, the snap coordinate is also transformed in the same way (such that the snap-point is aligned with the element as-drawn).</p>
345-
<p class="issue" id="issue-02f28956"><a class="self-link" href="#issue-02f28956"></a> How does this work with fragmentation? </p>
346345
<p class="issue" id="issue-0bada396"><a class="self-link" href="#issue-0bada396"></a> Consider alternative naming besides "coordinate". Consider naming conventions like in Grid Layout for grouping properties on the container vs. items. </p>
347346
<table class="definition propdef" data-link-for-hint="scroll-snap-coordinate">
348347
<tbody>
@@ -579,7 +578,6 @@ <h2 class="no-num heading settled" id="issues-index"><span class="content">Issue
579578
<div style="counter-reset:issue">
580579
<div class="issue"> Describe the guarantee as an invariant for better clarity. Include edge case behavior such as mandatory snap points when there is no satisfiable snap point. <a href="#issue-b2e1d9bc"></a></div>
581580
<div class="issue"> Should there be a way to specify that either end of the scrollable content should have a snap point? <a href="#issue-1011500c"></a></div>
582-
<div class="issue"> How does this work with fragmentation? <a href="#issue-02f28956"></a></div>
583581
<div class="issue"> Consider alternative naming besides "coordinate". Consider naming conventions like in Grid Layout for grouping properties on the container vs. items. <a href="#issue-0bada396"></a></div>
584582
</div>
585583
</body>

css-snappoints/Overview.src.html

Lines changed: 0 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -230,10 +230,6 @@ <h2 id="scroll-snap-coordinate">Scroll Snap Coordinate: the 'scroll-snap-coordin
230230
The 'scroll-snap-coordinate' property is used to define the x and y coordinate within the element
231231
which will align with the nearest ancestor <a>scroll container's</a> snap-destination for the respective axis. In the case that the element has been transformed, the snap coordinate is also transformed in the same way (such that the snap-point is aligned with the element as-drawn).
232232

233-
<p class="issue">
234-
How does this work with fragmentation?
235-
</p>
236-
237233
<p class="issue">
238234
Consider alternative naming besides "coordinate". Consider naming conventions like in Grid Layout for grouping properties on the container vs. items.
239235
</p>

0 commit comments

Comments
 (0)