From 70e17d384c156392d1f6a9bba668fa9328570f9e Mon Sep 17 00:00:00 2001
From: Florian Rivoal <git@florian.rivoal.net>
Date: Wed, 24 Jul 2019 22:07:00 +0200
Subject: [PATCH] [css-writing-modes-3] DoC update

---
 ...ssues-cr-2017.html => issues-cr-2018.html} | 20 +++++++++++--------
 ...{issues-cr-2017.txt => issues-cr-2018.txt} |  4 ++--
 2 files changed, 14 insertions(+), 10 deletions(-)
 rename css-writing-modes-3/{issues-cr-2017.html => issues-cr-2018.html} (92%)
 rename css-writing-modes-3/{issues-cr-2017.txt => issues-cr-2018.txt} (97%)

diff --git a/css-writing-modes-3/issues-cr-2017.html b/css-writing-modes-3/issues-cr-2018.html
similarity index 92%
rename from css-writing-modes-3/issues-cr-2017.html
rename to css-writing-modes-3/issues-cr-2018.html
index ba6232d84a0..47dbfe6a70f 100644
--- a/css-writing-modes-3/issues-cr-2017.html
+++ b/css-writing-modes-3/issues-cr-2018.html
@@ -31,15 +31,16 @@ <h1>CSS Writing Modes Level 3 Disposition of Comments for 2018-05-24 CR</h1>
 <p>An issue can be closed as <code>Accepted</code>, <code>OutOfScope</code>,
 <code>Invalid</code>, <code>Rejected</code>, or <code>Retracted</code>.
 <code>Verified</code> indicates commentor's acceptance of the response.</p>
-        <pre class=' open' id='issue-1'>
+        <pre class='a' id='issue-1'>
 Issue 1. <a href='#issue-1'>#</a>
 Summary:  White space processing in text-combine-horizontal
 From:     Yuki Seikguchi
 Comment:  <a href='https://lists.w3.org/Archives/Public/www-style/2018Aug/0011.html'>https://lists.w3.org/Archives/Public/www-style/2018Aug/0011.html</a>
 Comment:  <a href='https://github.com/w3c/csswg-drafts/issues/4139#issue-470826243'>https://github.com/w3c/csswg-drafts/issues/4139#issue-470826243</a>
 Response: <a href='https://github.com/w3c/csswg-drafts/issues/4139#issuecomment-513589921'>https://github.com/w3c/csswg-drafts/issues/4139#issuecomment-513589921</a>
-Open</pre>
-<pre class=' open' id='issue-2'>
+Closed:   Accepted (undefine in L3, solve in L4)
+Resolved: <a href='https://github.com/w3c/csswg-drafts/issues/4139#issuecomment-514701209'>https://github.com/w3c/csswg-drafts/issues/4139#issuecomment-514701209</a></pre>
+<pre class='d' id='issue-2'>
 Issue 2. <a href='#issue-2'>#</a>
 Summary:  Need to be clear about inputs to computation of min-content, max-content, and fit-content sizes
 From:     David Baron
@@ -47,7 +48,8 @@ <h1>CSS Writing Modes Level 3 Disposition of Comments for 2018-05-24 CR</h1>
 Comment:  <a href='https://github.com/w3c/csswg-drafts/issues/2890#issuecomment-420080835'>https://github.com/w3c/csswg-drafts/issues/2890#issuecomment-420080835</a>
 Comment:  <a href='https://github.com/w3c/csswg-drafts/issues/2890#issuecomment-420081451'>https://github.com/w3c/csswg-drafts/issues/2890#issuecomment-420081451</a>
 Comment:  <a href='https://github.com/w3c/csswg-drafts/issues/2890#issuecomment-420082478'>https://github.com/w3c/csswg-drafts/issues/2890#issuecomment-420082478</a>
-Open</pre>
+Closed:   Deferred
+Resolved: <a href='https://github.com/w3c/csswg-drafts/issues/4139#issuecomment-514701209'>https://github.com/w3c/csswg-drafts/issues/4139#issuecomment-514701209</a></pre>
 <pre class='a' id='issue-3'>
 Issue 3. <a href='#issue-3'>#</a>
 Summary:  Does vertical writing mode of an HTML body element cause an orthogonal flow?
@@ -57,12 +59,13 @@ <h1>CSS Writing Modes Level 3 Disposition of Comments for 2018-05-24 CR</h1>
 Response: <a href='https://github.com/w3c/csswg-drafts/pull/4130'>https://github.com/w3c/csswg-drafts/pull/4130</a>
 Closed:   Accepted
 Resolved: <a href='https://github.com/w3c/csswg-drafts/issues/3066#issuecomment-499111764'>https://github.com/w3c/csswg-drafts/issues/3066#issuecomment-499111764</a></pre>
-<pre class=' open' id='issue-4'>
+<pre class='d' id='issue-4'>
 Issue 4. <a href='#issue-4'>#</a>
 Summary:  Define “fixed size” as used to determine available space of orthogonal flows
 From:     Elika Etemad
 Comment:  <a href='https://github.com/w3c/csswg-drafts/issues/3095'>https://github.com/w3c/csswg-drafts/issues/3095</a>
-Open</pre>
+Closed:   Deferred
+Resolved: <a href='https://github.com/w3c/csswg-drafts/issues/4139#issuecomment-514701209'>https://github.com/w3c/csswg-drafts/issues/4139#issuecomment-514701209</a></pre>
 <pre class='a' id='issue-5'>
 Issue 5. <a href='#issue-5'>#</a>
 Summary:  Should writing-mode from display:contents element be applied to text?
@@ -123,12 +126,13 @@ <h1>CSS Writing Modes Level 3 Disposition of Comments for 2018-05-24 CR</h1>
 Closed:   Accepted
 Resolved: Editorial
 Verified: <a href='https://github.com/w3c/csswg-drafts/issues/3829#issuecomment-513626272'>https://github.com/w3c/csswg-drafts/issues/3829#issuecomment-513626272</a></pre>
-<pre class=' open' id='issue-12'>
+<pre class='d' id='issue-12'>
 Issue 12. <a href='#issue-12'>#</a>
 Summary:  "calculations that require a definite available inline space" unclear
 From:     David Baron
 Comment:  <a href='https://github.com/w3c/csswg-drafts/issues/4026'>https://github.com/w3c/csswg-drafts/issues/4026</a>
-Open</pre>
+Closed:   Deferred
+Resolved: <a href='https://github.com/w3c/csswg-drafts/issues/4139#issuecomment-514701209'>https://github.com/w3c/csswg-drafts/issues/4139#issuecomment-514701209</a></pre>
 <pre class='a' id='issue-13'>
 Issue 13. <a href='#issue-13'>#</a>
 Summary:  Vertical-align on table cells and writing-modes
diff --git a/css-writing-modes-3/issues-cr-2017.txt b/css-writing-modes-3/issues-cr-2018.txt
similarity index 97%
rename from css-writing-modes-3/issues-cr-2017.txt
rename to css-writing-modes-3/issues-cr-2018.txt
index 13196f8b17d..b9a955e4ee0 100644
--- a/css-writing-modes-3/issues-cr-2017.txt
+++ b/css-writing-modes-3/issues-cr-2018.txt
@@ -10,8 +10,8 @@ From:     Yuki Seikguchi
 Comment:  https://lists.w3.org/Archives/Public/www-style/2018Aug/0011.html
 Comment:  https://github.com/w3c/csswg-drafts/issues/4139#issue-470826243
 Response: https://github.com/w3c/csswg-drafts/issues/4139#issuecomment-513589921
-Open
-
+Closed:   Accepted (undefine in L3, solve in L4)
+Resolved: https://github.com/w3c/csswg-drafts/issues/4139#issuecomment-514701209
 ----
 Issue 2.
 Summary:  Need to be clear about inputs to computation of min-content, max-content, and fit-content sizes