[css-overflow] Record relationship with 'region-fragment' in an issue

Author: frivoal

css-overflow/Overview.bs

@@ -494,6 +494,10 @@ This was initially proposed as
 in <a href="https://lists.w3.org/Archives/Public/www-style/2015Jan/0357.html">https://lists.w3.org/Archives/Public/www-style/2015Jan/0357.html</a>,
 and there is not yet wide agreement as to which naming is better.
 
+Issue: This property is meant to generalize and replace 'region-fragment'.
+Once it is sufficiently stable in this specification,
+'region-fragment' should be removed from the regions specification in favor of this.
+
 Note: ''continue: fragments'' replaces "overflow:fragments"
 from earlier versions of this specification,
 while ''continue: paginate'' replaces "overflow: paged-x | paged-y | paged-x-controls | paged-y-controls"

css-overflow/Overview.html

@@ -1442,6 +1442,11 @@ <h2 class="heading settled" data-level="4" id="fragmentation"><span class="secno
 and there is not yet wide agreement as to which naming is better.</p>
 
 
+   <p class="issue" id="issue-d52b3e3d"><a class="self-link" href="#issue-d52b3e3d"></a>This property is meant to generalize and replace <a class="property" data-link-type="propdesc" href="http://dev.w3.org/csswg/css-regions-1/#propdef-region-fragment">region-fragment</a>.
+Once it is sufficiently stable in this specification,
+<a class="property" data-link-type="propdesc" href="http://dev.w3.org/csswg/css-regions-1/#propdef-region-fragment">region-fragment</a> should be removed from the regions specification in favor of this.</p>
+
+
    <p class="note" role="note">Note: <a class="css" data-link-type="propdesc" href="#propdef-continue">continue: fragments</a> replaces "overflow:fragments"
 from earlier versions of this specification,
 while <a class="css" data-link-type="propdesc" href="#propdef-continue">continue: paginate</a> replaces "overflow: paged-x | paged-y | paged-x-controls | paged-y-controls"</p>
@@ -2532,6 +2537,7 @@ <h3 class="no-num heading settled" id="index-defined-elsewhere"><span class="con
     <ul>
      <li><a href="http://dev.w3.org/csswg/css-regions-1/#css-region">css region</a>
      <li><a href="http://dev.w3.org/csswg/css-regions-1/#region-chain">region chain</a>
+     <li><a href="http://dev.w3.org/csswg/css-regions-1/#propdef-region-fragment">region-fragment</a>
     </ul>
    <li><a data-link-type="biblio" href="#biblio-css-text-decor-3">[css-text-decor-3]</a> defines the following terms:
     <ul>
@@ -2757,6 +2763,9 @@ <h2 class="no-num heading settled" id="issues-index"><span class="content">Issue
 "fragmentation: auto | none | break | clone | page"
 in <a href="https://lists.w3.org/Archives/Public/www-style/2015Jan/0357.html">https://lists.w3.org/Archives/Public/www-style/2015Jan/0357.html</a>,
 and there is not yet wide agreement as to which naming is better.<a href="#issue-b2c6e3da"> ↵ </a></div>
+   <div class="issue">This property is meant to generalize and replace <a class="property" data-link-type="propdesc" href="http://dev.w3.org/csswg/css-regions-1/#propdef-region-fragment">region-fragment</a>.
+Once it is sufficiently stable in this specification,
+<a class="property" data-link-type="propdesc" href="http://dev.w3.org/csswg/css-regions-1/#propdef-region-fragment">region-fragment</a> should be removed from the regions specification in favor of this.<a href="#issue-d52b3e3d"> ↵ </a></div>
    <div class="issue">When the element isn’t a <a data-link-type="dfn" href="http://dev.w3.org/csswg/css-break-3/#fragmentation-container">fragmentation container</a> already,
 		should this work by turning it directly into one,
 		or by creating a <a data-link-type="dfn" href="#fragment-box">fragment box</a> inside it like <a class="css" data-link-type="maybe" href="#valdef-continue-fragments">fragments</a> does?<a href="#issue-36be54be"> ↵ </a></div>