@@ -383,7 +383,8 @@ <h2 id=definitions><span class=secno>2. </span>Definitions</h2>
383383 < p > < dfn id =exclusion-area > Exclusion area</ dfn >
384384
385385 < div class =issue-marker data-bug_id =15087 data-bug_status =NEW > < a
386- href ="https://www.w3.org/Bugs/Public/show_bug.cgi?id=15087 "> Bug-15087</ a >
386+ href ="https://www.w3.org/Bugs/Public/show_bug.cgi?id=15087 "> Issue-15087</ a >
387+
387388 < div class =issue-details >
388389 < p class =short-desc > Interaction of floats and exclusions (Howcome's
389390 questions)</ p >
@@ -417,7 +418,8 @@ <h2 id=definitions><span class=secno>2. </span>Definitions</h2>
417418 < p > < dfn id =wrapping-context > Wrapping context</ dfn >
418419
419420 < div class =issue-marker data-bug_id =15086 data-bug_status =NEW > < a
420- href ="https://www.w3.org/Bugs/Public/show_bug.cgi?id=15086 "> Bug-15086</ a >
421+ href ="https://www.w3.org/Bugs/Public/show_bug.cgi?id=15086 "> Issue-15086</ a >
422+
421423 < div class =issue-details >
422424 < p class =short-desc > should the wrapping context be generic and include
423425 floats?</ p >
@@ -447,7 +449,8 @@ <h2 id=definitions><span class=secno>2. </span>Definitions</h2>
447449 arbitrary, non-rectangular content areas.
448450
449451 < div class =issue-marker data-bug_id =15089 data-bug_status =NEW > < a
450- href ="https://www.w3.org/Bugs/Public/show_bug.cgi?id=15089 "> Bug-15089</ a >
452+ href ="https://www.w3.org/Bugs/Public/show_bug.cgi?id=15089 "> Issue-15089</ a >
453+
451454 < div class =issue-details >
452455 < p class =short-desc > shrink-to-fit circle / shape</ p >
453456 </ div >
@@ -542,7 +545,8 @@ <h4 id=wrap-flow-property><span class=secno>3.1.1. </span>The ‘<a
542545 </ table >
543546
544547 < div class =issue-marker data-bug_id =16437 data-bug_status =ASSIGNED > < a
545- href ="https://www.w3.org/Bugs/Public/show_bug.cgi?id=16437 "> Bug-16437</ a >
548+ href ="https://www.w3.org/Bugs/Public/show_bug.cgi?id=16437 "> Issue-16437</ a >
549+
546550 < div class =issue-details >
547551 < p class =short-desc > Consistent use of start/end/top/bottom</ p >
548552 </ div >
@@ -638,7 +642,7 @@ <h4 id=wrap-flow-property><span class=secno>3.1.1. </span>The ‘<a
638642
639643 < div class ="issue-marker wrapper ">
640644 < div class =issue-marker data-bug_id =15088 data-bug_status =FIXED > < a
641- href ="https://www.w3.org/Bugs/Public/show_bug.cgi?id=15088 "> Bug -15088</ a >
645+ href ="https://www.w3.org/Bugs/Public/show_bug.cgi?id=15088 "> Issue -15088</ a >
642646
643647 < div class =issue-details >
644648 < p class =short-desc > Add an example with auto-height content and z-index
@@ -647,7 +651,7 @@ <h4 id=wrap-flow-property><span class=secno>3.1.1. </span>The ‘<a
647651 </ div >
648652
649653 < div class =issue-marker data-bug_id =15084 data-bug_status =NEW > < a
650- href ="https://www.w3.org/Bugs/Public/show_bug.cgi?id=15084 "> Bug -15084</ a >
654+ href ="https://www.w3.org/Bugs/Public/show_bug.cgi?id=15084 "> Issue -15084</ a >
651655
652656 < div class =issue-details >
653657 < p class =short-desc > Fluidity of the layout with respect to different
@@ -904,7 +908,8 @@ <h4 id=wrap-through-property><span class=secno>3.3.1. </span>The ‘<a
904908 Property</ h4 >
905909
906910 < div class =issue-marker data-bug_id =15085 data-bug_status =NEW > < a
907- href ="https://www.w3.org/Bugs/Public/show_bug.cgi?id=15085 "> Bug-15085</ a >
911+ href ="https://www.w3.org/Bugs/Public/show_bug.cgi?id=15085 "> Issue-15085</ a >
912+
908913 < div class =issue-details >
909914 < p class =short-desc > do we need wrap-through?</ p >
910915 </ div >
@@ -1104,7 +1109,8 @@ <h3 id=exclusions-order><span class=secno>3.4. </span>Exclusions order</h3>
11041109 order.
11051110
11061111 < div class =issue-marker data-bug_id =16474 data-bug_status =NEW > < a
1107- href ="https://www.w3.org/Bugs/Public/show_bug.cgi?id=16474 "> Bug-16474</ a >
1112+ href ="https://www.w3.org/Bugs/Public/show_bug.cgi?id=16474 "> Issue-16474</ a >
1113+
11081114 < div class =issue-details >
11091115 < p class =short-desc > Improve Example 3 about exclusion order</ p >
11101116 </ div >
@@ -1155,15 +1161,15 @@ <h3 id=exclusions-order><span class=secno>3.4. </span>Exclusions order</h3>
11551161
11561162 < div class ="issue-marker wrapper ">
11571163 < div class =issue-marker data-bug_id =15183 data-bug_status =NEW > < a
1158- href ="https://www.w3.org/Bugs/Public/show_bug.cgi?id=15183 "> Bug -15183</ a >
1164+ href ="https://www.w3.org/Bugs/Public/show_bug.cgi?id=15183 "> Issue -15183</ a >
11591165
11601166 < div class =issue-details >
11611167 < p class =short-desc > Is the CSS exclusions processing model incorrect?</ p >
11621168 </ div >
11631169 </ div >
11641170
11651171 < div class =issue-marker data-bug_id =15083 data-bug_status =NEW > < a
1166- href ="https://www.w3.org/Bugs/Public/show_bug.cgi?id=15083 "> Bug -15083</ a >
1172+ href ="https://www.w3.org/Bugs/Public/show_bug.cgi?id=15083 "> Issue -15083</ a >
11671173
11681174 < div class =issue-details >
11691175 < p class =short-desc > Concerns over Error accumulation vs. performance</ p >
@@ -1531,15 +1537,15 @@ <h2 id=shapes><span class=secno>4. </span>Shapes</h2>
15311537
15321538 < div class ="issue-marker wrapper ">
15331539 < div class =issue-marker data-bug_id =15091 data-bug_status =NEW > < a
1534- href ="https://www.w3.org/Bugs/Public/show_bug.cgi?id=15091 "> Bug -15091</ a > < br >
1540+ href ="https://www.w3.org/Bugs/Public/show_bug.cgi?id=15091 "> Issue -15091</ a > < br >
15351541
15361542 < div class =issue-details >
15371543 < p class =short-desc > Simplify the syntax for shapes</ p >
15381544 </ div >
15391545 </ div >
15401546
15411547 < div class =issue-marker data-bug_id =16716 data-bug_status =NEW > < a
1542- href ="https://www.w3.org/Bugs/Public/show_bug.cgi?id=16716 "> Bug -16716</ a >
1548+ href ="https://www.w3.org/Bugs/Public/show_bug.cgi?id=16716 "> Issue -16716</ a >
15431549
15441550 < div class =issue-details >
15451551 < p class =short-desc > Handling visible content as a shape for Exclusions</ p >
@@ -1769,7 +1775,7 @@ <h3 id=shapes-from-image><span class=secno>4.3. </span>Shapes from Image</h3>
17691775
17701776 < div class ="issue-marker wrapper ">
17711777 < div class =issue-marker data-bug_id =15093 data-bug_status =NEW > < a
1772- href ="https://www.w3.org/Bugs/Public/show_bug.cgi?id=15093 "> Bug -15093</ a > < br >
1778+ href ="https://www.w3.org/Bugs/Public/show_bug.cgi?id=15093 "> Issue -15093</ a > < br >
17731779
17741780 < div class =issue-details >
17751781 < p class =short-desc > Do we need to provide properties to repeat
@@ -1778,7 +1784,7 @@ <h3 id=shapes-from-image><span class=secno>4.3. </span>Shapes from Image</h3>
17781784 </ div >
17791785
17801786 < div class =issue-marker data-bug_id =15090 data-bug_status =NEW > < a
1781- href ="https://www.w3.org/Bugs/Public/show_bug.cgi?id=15090 "> Bug -15090</ a > < br >
1787+ href ="https://www.w3.org/Bugs/Public/show_bug.cgi?id=15090 "> Issue -15090</ a > < br >
17821788
17831789 < div class =issue-details >
17841790 < p class =short-desc > Use the contour() keyword. <img id=shape-me
@@ -1789,15 +1795,15 @@ <h3 id=shapes-from-image><span class=secno>4.3. </span>Shapes from Image</h3>
17891795 </ div >
17901796
17911797 < div class =issue-marker data-bug_id =15092 data-bug_status =NEW > < a
1792- href ="https://www.w3.org/Bugs/Public/show_bug.cgi?id=15092 "> Bug -15092</ a >
1798+ href ="https://www.w3.org/Bugs/Public/show_bug.cgi?id=15092 "> Issue -15092</ a >
17931799
17941800 < div class =issue-details >
17951801 < p class =short-desc > Specify what happens with animated images</ p >
17961802 </ div >
17971803 </ div >
17981804
17991805 < div class =issue-marker data-bug_id =16112 data-bug_status =NEW > < a
1800- href ="https://www.w3.org/Bugs/Public/show_bug.cgi?id=16112 "> Bug -16112</ a >
1806+ href ="https://www.w3.org/Bugs/Public/show_bug.cgi?id=16112 "> Issue -16112</ a >
18011807
18021808 < div class =issue-details >
18031809 < p class =short-desc > Address security concern with automatic shape
@@ -2019,7 +2025,7 @@ <h4 id=shape-inside-property><span class=secno>4.4.2. </span>The ‘<a
20192025
20202026 < div class ="issue-marker wrapper ">
20212027 < div class =issue-marker data-bug_id =16448 data-bug_status =ASSIGNED > < a
2022- href ="https://www.w3.org/Bugs/Public/show_bug.cgi?id=16448 "> Bug -16448</ a >
2028+ href ="https://www.w3.org/Bugs/Public/show_bug.cgi?id=16448 "> Issue -16448</ a >
20232029
20242030 < div class =issue-details >
20252031 < p class =short-desc > Should we revisit the decision to not allow SVG path
@@ -2028,7 +2034,7 @@ <h4 id=shape-inside-property><span class=secno>4.4.2. </span>The ‘<a
20282034 </ div >
20292035
20302036 < div class =issue-marker data-bug_id =16460 data-bug_status =NEW > < a
2031- href ="https://www.w3.org/Bugs/Public/show_bug.cgi?id=16460 "> Bug -16460</ a >
2037+ href ="https://www.w3.org/Bugs/Public/show_bug.cgi?id=16460 "> Issue -16460</ a >
20322038
20332039 < div class =issue-details >
20342040 < p class =short-desc > Specify overflow behavior for shape-inside</ p >
@@ -2773,7 +2779,7 @@ <h2 class=no-num id=property-index>Property index</h2>
27732779
27742780 < div class =issue-marker data-bug_id ="{{bug_id}} "
27752781 data-bug_status ="{{bug_status}} "> < a
2776- href ="https://www.w3.org/Bugs/Public/show_bug.cgi?id={{bug_id}} "> Bug -{{bug_id}}</ a >
2782+ href ="https://www.w3.org/Bugs/Public/show_bug.cgi?id={{bug_id}} "> Issue -{{bug_id}}</ a >
27772783
27782784 < div class =issue-details >
27792785 < p class =short-desc > {{short_desc}}</ p >
0 commit comments