@@ -356,7 +356,7 @@ <h2 id=introduction><span class=secno>1. </span>Introduction</h2>
356356 < p > < em > This section is non-normative.</ em >
357357
358358 < div class =issue-marker > < a
359- href ="https://www.w3.org/Bugs/Public/show_bug.cgi?15159 "> Bug-15159</ a >
359+ href ="https://www.w3.org/Bugs/Public/show_bug.cgi?id= 15159 "> Bug-15159</ a >
360360 < div class =issue-details >
361361 < p class =short-desc > Add code samples to the CSS regions use cases page</ p >
362362 </ div >
@@ -377,7 +377,7 @@ <h2 id=introduction><span class=secno>1. </span>Introduction</h2>
377377 the flow is made of the multi-column element's children.
378378
379379 < div class =issue-marker > < a
380- href ="https://www.w3.org/Bugs/Public/show_bug.cgi?15733 "> Bug-15733</ a >
380+ href ="https://www.w3.org/Bugs/Public/show_bug.cgi?id= 15733 "> Bug-15733</ a >
381381 < div class =issue-details >
382382 < p class =short-desc > Should the region specification define a mechanism to
383383 create blocks that can be regions with CSS syntax?</ p >
@@ -404,7 +404,7 @@ <h3 id=named-flows-and-regions><span class=secno>1.1. </span>Named flows
404404 </ div >
405405
406406 < div class =issue-marker > < a
407- href ="https://www.w3.org/Bugs/Public/show_bug.cgi?15131 "> Bug-15131</ a >
407+ href ="https://www.w3.org/Bugs/Public/show_bug.cgi?id= 15131 "> Bug-15131</ a >
408408 < div class =issue-details >
409409 < p class =short-desc > Add layout to initial example</ p >
410410 </ div >
@@ -563,7 +563,7 @@ <h2 id=css-regions-concepts><span class=secno>2. </span>CSS regions
563563 < h3 id =regions > < span class =secno > 2.1. </ span > Regions</ h3 >
564564
565565 < div class =issue-marker > < a
566- href ="https://www.w3.org/Bugs/Public/show_bug.cgi?15186 "> Bug-15186</ a >
566+ href ="https://www.w3.org/Bugs/Public/show_bug.cgi?id= 15186 "> Bug-15186</ a >
567567 < div class =issue-details >
568568 < p class =short-desc > Is a mechanism to auto-generate regions necessary in
569569 order to support reusable style sheets?</ p >
@@ -637,7 +637,7 @@ <h3 id=the-flow-into-property><span class=secno>4.1. </span>The ‘<a
637637 property</ h3 >
638638
639639 < div class =issue-marker > < a
640- href ="https://www.w3.org/Bugs/Public/show_bug.cgi?15811 "> Bug-15811</ a >
640+ href ="https://www.w3.org/Bugs/Public/show_bug.cgi?id= 15811 "> Bug-15811</ a >
641641 < div class =issue-details >
642642 < p class =short-desc > Creating a named flow from external resource</ p >
643643 </ div >
@@ -786,7 +786,7 @@ <h3 id=the-flow-from-property><span class=secno>4.2. </span>The ‘<a
786786 region and associates it with a named flow.
787787
788788 < div class =issue-marker > < a
789- href ="https://www.w3.org/Bugs/Public/show_bug.cgi?15191 "> Bug-15191</ a >
789+ href ="https://www.w3.org/Bugs/Public/show_bug.cgi?id= 15191 "> Bug-15191</ a >
790790 < div class =issue-details >
791791 < p class =short-desc > Should we allow multi-column elements to be regions?</ p >
792792 </ div >
@@ -897,15 +897,17 @@ <h3 id=the-flow-from-property><span class=secno>4.2. </span>The ‘<a
897897 visually.</ div >
898898
899899 < div class =issue-marker > < a
900- href ="https://www.w3.org/Bugs/Public/show_bug.cgi?15189 "> Bug-15189</ a >
900+ href ="https://www.w3.org/Bugs/Public/show_bug.cgi?id= 15189 "> Bug-15189</ a >
901901 < div class =issue-details >
902902 < p class =short-desc > Should regions be non-breakable?</ p >
903903 </ div >
904- < a href ="https://www.w3.org/Bugs/Public/show_bug.cgi?15824 "> Bug-15824</ a >
904+ < a
905+ href ="https://www.w3.org/Bugs/Public/show_bug.cgi?id=15824 "> Bug-15824</ a >
905906 < div class =issue-details >
906907 < p class =short-desc > Should regions not create a new stacking context?</ p >
907908 </ div >
908- < a href ="https://www.w3.org/Bugs/Public/show_bug.cgi?15824 "> Bug-15827</ a >
909+ < a
910+ href ="https://www.w3.org/Bugs/Public/show_bug.cgi?id=15824 "> Bug-15827</ a >
909911 < div class =issue-details >
910912 < p class =short-desc > Specify behavior of stacking contexts that are split
911913 between regions</ p >
@@ -971,7 +973,7 @@ <h4 id=auto-width-on-regions><span class=secno>4.2.1. </span>Auto width on
971973 regions</ h4 >
972974
973975 < div class =issue-marker > < a
974- href ="https://www.w3.org/Bugs/Public/show_bug.cgi?15741 "> Bug-15741</ a >
976+ href ="https://www.w3.org/Bugs/Public/show_bug.cgi?id= 15741 "> Bug-15741</ a >
975977 < div class =issue-details >
976978 < p class =short-desc > Regions intrinsic size</ p >
977979 </ div >
@@ -1213,6 +1215,14 @@ <h3 id=the-region-overflow-property><span class=secno>4.4. </span>The
12131215 < td > specified value
12141216 </ table >
12151217
1218+ < div class =issue-marker > < a
1219+ href ="https://www.w3.org/Bugs/Public/show_bug.cgi?id=15832 "> Bug-15832</ a >
1220+ < div class =issue-details >
1221+ < p class =short-desc > Should we have region-overflow:nobreak and have
1222+ region-overflow apply to all regions, not just the last?</ p >
1223+ </ div >
1224+ </ div >
1225+
12161226 < p > The ‘< a href ="#region-overflow "> < code
12171227 class =property > region-overflow</ code > </ a > ’ property controls the
12181228 behavior of the < em id =last-region > last region</ em > associated with a < a
@@ -1350,7 +1360,7 @@ <h3 id=the-at-region-style-rule><span class=secno>4.5. </span>The @region
13501360 from the region's flow that flows in the selected region(s).
13511361
13521362 < div class =issue-marker > < a
1353- href ="https://www.w3.org/Bugs/Public/show_bug.cgi?15713 "> Bug-15713</ a >
1363+ href ="https://www.w3.org/Bugs/Public/show_bug.cgi?id= 15713 "> Bug-15713</ a >
13541364 < div class =issue-details >
13551365 < p class =short-desc > Model for styling element fragments</ p >
13561366 </ div >
@@ -1364,7 +1374,7 @@ <h3 id=the-at-region-style-rule><span class=secno>4.5. </span>The @region
13641374 < p > Only a limited list of properties can be set in a region style rule:
13651375
13661376 < div class =issue-marker > < a
1367- href ="https://www.w3.org/Bugs/Public/show_bug.cgi?15190 "> Bug-15190</ a >
1377+ href ="https://www.w3.org/Bugs/Public/show_bug.cgi?id= 15190 "> Bug-15190</ a >
13681378 < div class =issue-details >
13691379 < p class =short-desc > List of region style properties</ p >
13701380 </ div >
@@ -1520,7 +1530,7 @@ <h3 id=the-at-region-style-rule><span class=secno>4.5. </span>The @region
15201530 </ div >
15211531
15221532 < div class =issue-marker > < a
1523- href ="https://www.w3.org/Bugs/Public/show_bug.cgi?15734 "> Bug-15734</ a >
1533+ href ="https://www.w3.org/Bugs/Public/show_bug.cgi?id= 15734 "> Bug-15734</ a >
15241534 < div class =issue-details >
15251535 < p class =short-desc > @region and specificity</ p >
15261536 </ div >
@@ -1554,7 +1564,7 @@ <h3 id=the-at-region-style-rule><span class=secno>4.5. </span>The @region
15541564 < h2 id ="pseudo_elements "> < span class =secno > 5. </ span > Pseudo-elements</ h2 >
15551565
15561566 < div class =issue-marker > < a
1557- href ="https://www.w3.org/Bugs/Public/show_bug.cgi?15188 "> Bug-15188</ a >
1567+ href ="https://www.w3.org/Bugs/Public/show_bug.cgi?id= 15188 "> Bug-15188</ a >
15581568 < div class =issue-details >
15591569 < p class =short-desc > add functionality for having textual describtion like
15601570 "continued here" or "continued on page x" to regions.</ p >
@@ -1604,7 +1614,7 @@ <h2 id="cssom_view_and_css_regions"><span class=secno>6. </span>CSSOM view
16041614 and CSS regions</ h2 >
16051615
16061616 < div class =issue-marker > < a
1607- href ="https://www.w3.org/Bugs/Public/show_bug.cgi?15679 "> Bug-15679</ a >
1617+ href ="https://www.w3.org/Bugs/Public/show_bug.cgi?id= 15679 "> Bug-15679</ a >
16081618 < div class =issue-details >
16091619 < p class =short-desc > elementFromPoint and CSS regions</ p >
16101620 </ div >
@@ -1618,7 +1628,7 @@ <h2 id="cssom_view_and_css_regions"><span class=secno>6. </span>CSSOM view
16181628 than on a large desktop display.
16191629
16201630 < div class =issue-marker > < a
1621- href ="https://www.w3.org/Bugs/Public/show_bug.cgi?15010 "> Bug-15010</ a >
1631+ href ="https://www.w3.org/Bugs/Public/show_bug.cgi?id= 15010 "> Bug-15010</ a >
16221632 < div class =issue-details >
16231633 < p class =short-desc > Need to add a CSSRegionRule to Region OM</ p >
16241634 </ div >
@@ -1641,7 +1651,7 @@ <h3 id=the-namedflow-interface><span class=secno>6.1. </span>The NamedFlow
16411651 interface</ h3 >
16421652
16431653 < div class =issue-marker > < a
1644- href ="https://www.w3.org/Bugs/Public/show_bug.cgi?14948 "> Bug-14948</ a >
1654+ href ="https://www.w3.org/Bugs/Public/show_bug.cgi?id= 14948 "> Bug-14948</ a >
16451655 < div class =issue-details >
16461656 < p class =short-desc > What should getFlowByName return if there is no flow
16471657 with the given name?</ p >
@@ -1674,7 +1684,7 @@ <h3 id=the-namedflow-interface><span class=secno>6.1. </span>The NamedFlow
16741684 < a href ="#named-flow0 "> named flow</ a > instances.
16751685
16761686 < div class =issue-marker > < a
1677- href ="https://www.w3.org/Bugs/Public/show_bug.cgi?15828 "> Bug-15828</ a >
1687+ href ="https://www.w3.org/Bugs/Public/show_bug.cgi?id= 15828 "> Bug-15828</ a >
16781688 < div class =issue-details >
16791689 < p class =short-desc > Should add a ‘< a
16801690 href ="#dom-namedflow-name "> < code class =property > name</ code > </ a > ’
@@ -1840,7 +1850,7 @@ <h3 id=region-flow-layout-events><span class=secno>6.3. </span>Region flow
18401850 layout events</ h3 >
18411851
18421852 < div class =issue-marker > < a
1843- href ="https://www.w3.org/Bugs/Public/show_bug.cgi?15009 "> Bug-15009</ a >
1853+ href ="https://www.w3.org/Bugs/Public/show_bug.cgi?id= 15009 "> Bug-15009</ a >
18441854 < div class =issue-details >
18451855 < p class =short-desc > Should we have additional events for CSS Regions?</ p >
18461856 </ div >
0 commit comments