[css-display-3] Update DoC

Author: fantasai

css-display-3/issues-wd-2017.bsi

@@ -1,4 +1,4 @@
-Draft:    hhttps://www.w3.org/TR/2015/WD-css-display-3-20151015/
+Draft:    https://www.w3.org/TR/2015/WD-css-display-3-20151015/
 Title:    CSS Display Module Level 3
 
 Note: There were also issues on box-suppress, but it has been deferred to a future level to enable further work.
@@ -503,3 +503,324 @@ From:     Oriol
 Comment:  https://github.com/w3c/csswg-drafts/issues/1550
 Open
 ----
+Issue 61.
+Summary:  Is the principal box unique?
+From:     Oriol
+Comment:  https://github.com/w3c/csswg-drafts/issues/1604
+Response: https://github.com/w3c/csswg-drafts/issues/1604#issuecomment-374366647
+Closed:   OutOfScope
+Notes:    Follow-up for css-flow-3 https://github.com/w3c/csswg-drafts/issues/1477
+----
+Issue 62.
+Summary:  run-in fixup should create inline-block when parent inlinifies
+From:     Oriol
+Comment:  https://github.com/w3c/csswg-drafts/issues/1607
+Response: https://github.com/w3c/csswg-drafts/issues/1607#issuecomment-374368323
+Closed:   Invalid
+----
+Issue 63.
+Summary:  Define how block containers establish an inline formatting context
+From:     Oriol
+Comment:  https://github.com/w3c/csswg-drafts/issues/1617
+Response: https://github.com/w3c/csswg-drafts/issues/1617#issuecomment-374369526
+Closed:   Accepted
+Verified: https://github.com/w3c/csswg-drafts/issues/1617#issuecomment-374376423
+Comment:  https://github.com/w3c/csswg-drafts/issues/1617#issuecomment-374385637
+Response: https://github.com/w3c/csswg-drafts/issues/1617#issuecomment-398958073
+Resolved: Editor discretion
+----
+Issue 64.
+Summary:  Position of 'list-item' when serializing 'display'
+From:     Oriol
+Comment:  https://github.com/w3c/csswg-drafts/issues/1621
+Response: https://github.com/w3c/csswg-drafts/issues/1621#issuecomment-374730492
+Closed:   Accepted
+Resolved: Bugfix
+----
+Issue 65.
+Summary:  Clarify that outer display type only affects principal box
+From:     Oriol
+Comment:  https://github.com/w3c/csswg-drafts/issues/1622
+Changes:  https://github.com/w3c/csswg-drafts/commit/c5d8900d4cc8dedd4f7a02d506d0e0cd2cb5a639
+Closed:   Accepted
+Resolved: Editorial
+----
+Issue 66.
+Summary:  Compact at-risk list
+From:     Oriol
+Comment:  https://github.com/w3c/csswg-drafts/issues/1623
+Changes:  https://github.com/w3c/csswg-drafts/commit/9f72f245cba50a173813c36b771f552fe8104964
+Closed:   Accepted
+Resolved: Editorial
+----
+Issue 67.
+Summary:  list-item generates ::marker pseudo-element (not necessarily box)
+From:     Oriol
+Comment:  https://github.com/w3c/csswg-drafts/issues/1625
+Changes:  https://github.com/w3c/csswg-drafts/commit/ed5c6a31724e014f3336dbf7901c5ef5cb1eaf20
+Closed:   Accepted
+Resolved: Bugfix
+----
+Issue 68.
+Summary:  Mismatched references (to CSS2 vs css-lists-3)
+From:     Oriol
+Comment:  https://github.com/w3c/csswg-drafts/issues/1626
+Response: https://github.com/w3c/csswg-drafts/issues/1626#issuecomment-374373751
+Changes:  https://github.com/w3c/csswg-drafts/commit/7af6650e9ad441bac22fe833cb413112262f9149
+Closed:   Accepted
+Resolved: Editorial
+----
+Issue 69.
+Summary:  Mention that block ruby generates principal block box
+From:     Oriol
+Comment:  https://github.com/w3c/csswg-drafts/issues/1629
+Changes:  https://github.com/w3c/csswg-drafts/commit/5e90348a26aecbed6d878cce89cbbc7db1b058ff
+Closed:   Accepted
+Resolved: Bugfix
+----
+Issue 70.
+Summary:  run-in insertion point vs ::marker with 'display'
+From:     Oriol
+Comment:  https://github.com/w3c/csswg-drafts/issues/1638
+Response: https://github.com/w3c/csswg-drafts/issues/1638#issuecomment-316979494
+Closed:   Retracted
+----
+Issue 71.
+Summary:  Are run-in sequences merged during reparenting?
+From:     Oriol
+Comment:  https://github.com/w3c/csswg-drafts/issues/1639
+Changes:  https://github.com/w3c/csswg-drafts/commit/ef3c8fd8b2fe85c32a2dc393ca3b2810a414ea88
+Closed:   Accepted
+Resolved: Editorial
+----
+Issue 72.
+Summary:  Clarify run-in recursion vs anonymous-block wrapping
+From:     Oriol
+Comment:  https://github.com/w3c/csswg-drafts/issues/1640
+Response: https://github.com/w3c/csswg-drafts/issues/1640#issuecomment-374384660
+Changes:  https://github.com/w3c/csswg-drafts/commit/c7841af7ab963a5e91b2436ffe60ece80700cc7e
+Closed:   Accepted
+Comment:  https://github.com/w3c/csswg-drafts/issues/1640#issuecomment-374390920
+Response: https://github.com/w3c/csswg-drafts/issues/1640#issuecomment-398963365
+Closed:   Rejected
+Resolved: Editorial
+----
+Issue 73.
+Summary:  Define inner display type of replaced elements
+From:     Oriol
+Comment:  https://github.com/w3c/csswg-drafts/issues/1642
+Response: https://github.com/w3c/csswg-drafts/issues/1642#issuecomment-374399290
+Closed:   Invalid
+----
+Issue 74.
+Summary:  How does inner display type compute on replaced elements if out of scope?
+From:     Sebastien Zartner
+Comment:  https://github.com/w3c/csswg-drafts/issues/1642#issuecomment-317237475
+Response: https://github.com/w3c/csswg-drafts/issues/1642#issuecomment-398964350
+Open:     =Tab= Check if we need to edit anything?
+Resolved: Editorial
+----
+Issue 75.
+Summary:  Define style computation reflection between boxes and elements
+From:     Oriol
+Comment:  https://github.com/w3c/csswg-drafts/issues/1643
+Response: https://github.com/w3c/csswg-drafts/issues/1643#issuecomment-350398313
+Comment:  https://github.com/w3c/csswg-drafts/issues/1702
+Response: https://github.com/w3c/csswg-drafts/issues/1702#issuecomment-374415941
+Changes:  https://github.com/w3c/csswg-drafts/commit/b2d484c6ab9c4dbdb8fdca899e2d37d59d6953e3
+Closed:   Accepted
+Resolved: https://lists.w3.org/Archives/Public/www-style/2018Apr/0005.html
+----
+Issue 76.
+Summary:  Define some box construction guidance for specs
+From:     Oriol
+Comment:  https://github.com/w3c/csswg-drafts/issues/1643
+Response: https://github.com/w3c/csswg-drafts/issues/1643#issuecomment-350398313
+Changes:  https://github.com/w3c/csswg-drafts/commit/533ac0a31b0262c4a0d09c77e19604666fe35e14
+Resolved: https://lists.w3.org/Archives/Public/www-style/2018Apr/0005.html
+----
+Issue 77.
+Summary:  table grid box is not a defined term
+From:     David Baron
+Comment:  https://github.com/w3c/csswg-drafts/issues/1643#issuecomment-376733708
+Response: https://github.com/w3c/csswg-drafts/issues/1643#issuecomment-378768000
+Changes:  https://github.com/w3c/csswg-drafts/commit/193022f623acd1b95a1fddae76fd98408a618d8b
+Closed:   Accepted
+Resolved: Editorial
+----
+Issue 78.
+Summary:  Rename table box to table grid box (in CSS2 & CSS Tables L3)
+From:     fantasai
+Comment:  https://github.com/w3c/csswg-drafts/issues/2501
+Response: https://github.com/w3c/csswg-drafts/issues/2501#issuecomment-380792875
+Open:     Changing back is pending edits to CSS2 and css-tables-3
+Resolved: https://lists.w3.org/Archives/Public/www-style/2018May/0044.html
+----
+Issue 79.
+Summary:  Boxes shouldn't have display types, should only have levels/FC-types
+From:     Oriol
+Comment:  https://github.com/w3c/csswg-drafts/issues/1643#issuecomment-374423595
+Open
+----
+Issue 80.
+Summary:  Explicitly exclude non-zero sequences of run-ins from processing
+From:     Oriol
+Comment:  https://github.com/w3c/csswg-drafts/issues/1663
+Response: https://github.com/w3c/csswg-drafts/issues/1663#issuecomment-398970537
+Open
+----
+Issue 81.
+Summary:  Link to definition of white space
+From:     Oriol
+Comment:  https://github.com/w3c/csswg-drafts/issues/1664
+Changes:  https://github.com/w3c/csswg-drafts/commit/ada381e196c8ed510977cb55916ee5fb96447b25
+Closed:   Accepted
+Resolved: Bugfix
+----
+Issue 82.
+Summary:  s/text/text run/ now that text run is defined
+From:     Oriol
+Comment:  https://github.com/w3c/csswg-drafts/issues/1667
+Changes:  https://github.com/w3c/csswg-drafts/commit/c3a695c65170e1667090d87310b87df79d93d398
+Closed:   Accepted
+Resolved: Editorial
+----
+Issue 83.
+Summary:  What if containing block is not ICB and not generated from a box?
+From:     Oriol
+Comment:  https://github.com/w3c/csswg-drafts/issues/1672
+Response: https://github.com/w3c/csswg-drafts/issues/1672#issuecomment-319916887
+Closed:   Invalid
+Comment:  https://github.com/w3c/csswg-drafts/issues/1672#issuecomment-350404179
+Response: https://github.com/w3c/csswg-drafts/issues/1672#issuecomment-374790036
+Closed:   Rejected
+Resolved: Editor discretion
+----
+Issue 84.
+Summary:  Make inlinified 'block ruby' an inline-block instead of inline
+From:     Oriol
+Comment:  https://github.com/w3c/csswg-drafts/issues/1700
+Response: https://github.com/w3c/csswg-drafts/issues/1700#issuecomment-374415499
+Closed:   Rejected
+Resolved: Editor discretion
+----
+Issue 85.
+Summary:  'block' only generates block-level boxes in flow layout
+From:     Oriol
+Comment:  https://github.com/w3c/csswg-drafts/issues/1704
+Response: https://github.com/w3c/csswg-drafts/issues/1704#issuecomment-374418771
+Changes:  https://github.com/w3c/csswg-drafts/commit/4358d72a927b265d9b7482a57277dc635c076b76
+Closed:   Accepted
+Resolved: Bugfix
+----
+Issue 86.
+Summary:  Clarify blockification of 'run-in flow-root'
+From:     Oriol
+Comment:  https://github.com/w3c/csswg-drafts/issues/1715
+Response: https://github.com/w3c/csswg-drafts/issues/1715#issuecomment-374420463
+Closed:   Accepted
+Resolved: https://lists.w3.org/Archives/Public/www-style/2018Apr/0005.html
+----
+Issue 87.
+Summary:  'display' computed value wrong in propdef table
+From:     Oriol
+Comment:  https://github.com/w3c/csswg-drafts/issues/1716
+Changes:  https://github.com/w3c/csswg-drafts/issues/1716
+Closed:   Accepted
+Resolved: Bugfix
+----
+Issue 89.
+Summary:  Do empty text nodes generate text runs?
+From:     Oriol
+Comment:  https://github.com/w3c/csswg-drafts/issues/1808
+Response: https://github.com/w3c/csswg-drafts/issues/1808#issuecomment-329345715
+Changes:  https://github.com/w3c/csswg-drafts/commit/4c21a2aa923a757c577bf4a4e33a6291a78c8690
+Closed:   Accepted
+----
+Issue 90.
+Summary:  Clarify element tree definition
+From:     Oriol
+Comment:  https://github.com/w3c/csswg-drafts/issues/1810
+Response: https://github.com/w3c/csswg-drafts/issues/1810#issuecomment-375137826
+Closed:   OutOfScope
+Resolved: https://lists.w3.org/Archives/Public/www-style/2018May/0036.html
+----
+Issue 91.
+Summary:  SVG 'display: contents' interaction incompletely defined
+From:     Rune Lillesveen
+Comment:  https://github.com/w3c/csswg-drafts/issues/2118
+Response: https://github.com/w3c/csswg-drafts/issues/2118#issuecomment-374802030
+Changes:  https://github.com/w3c/csswg-drafts/commit/2cdf747bbbfe0c58a87455beca9c35b72555b09a
+Closed:   Accepted
+----
+Issue 92.
+Summary:  Define interaction of 'display: contents' and MathML
+From:     Emilio Álvarez
+Comment:  https://github.com/w3c/csswg-drafts/issues/2167
+Response: https://github.com/w3c/csswg-drafts/issues/2167#issuecomment-375119086
+Changes:  https://github.com/w3c/csswg-drafts/commit/1d3e6a04c847df82fa3c4023e23f4ea55dcab169
+Verified: https://github.com/w3c/csswg-drafts/issues/2167#issuecomment-375792285
+Resolved: https://lists.w3.org/Archives/Public/www-style/2018Apr/0005.html
+----
+Issue 93.
+Summary:  Does 'display' affect screen reader semantics?
+From:     Ilya Streltsyn
+Comment:  https://github.com/w3c/csswg-drafts/issues/2355
+Response: https://github.com/w3c/csswg-drafts/issues/2355#issuecomment-368287740
+Response: https://github.com/w3c/csswg-drafts/issues/2355#issuecomment-375084853
+Comment:  https://github.com/w3c/csswg-drafts/issues/2355#issuecomment-378670370
+Response: https://github.com/w3c/csswg-drafts/issues/2355#issuecomment-378778909
+Closed:   Accepted
+Resolved: Editorial
+----
+Issue 94.
+Summary:  Does 'display: contents' affect anchor targeting?
+From:     Ilya Streltsyn
+Comment:  https://github.com/w3c/csswg-drafts/issues/2355#issuecomment-378842501
+Response: https://github.com/w3c/csswg-drafts/issues/2355#issuecomment-378992876
+Changes:  https://github.com/fergald/csswg-drafts/commit/2343af6382b55e8ce5caf9c0ee40d68ef032b421
+Closed:   Accepted
+Resolved: Editor discretion
+----
+Issue 95.
+Summary:  Effect of 'display: contents' on SVG layout attributes
+From:     Amelia Bellamy-Royds
+Comment:  https://github.com/w3c/csswg-drafts/issues/2502
+Response: https://github.com/w3c/csswg-drafts/issues/2502#issuecomment-378809174
+Open
+----
+Issue 96.
+Summary:  Integrate definition of Shadow Trees
+From:     Anne van Kesteren
+Comment:  https://github.com/w3c/csswg-drafts/issues/2365
+Open:     OutOfScope
+Resolved: https://lists.w3.org/Archives/Public/www-style/2018May/0036.html
+----
+Issue 97.
+Summary:  Blockification should establish a new formatting context
+From:     Oriol
+Comment:  https://github.com/w3c/csswg-drafts/issues/2598
+Response: https://github.com/w3c/csswg-drafts/issues/2598#issuecomment-387157017
+Closed:   Invalid
+----
+Issue 98.
+Summary:  Swap where default inner/outer display types are defined
+From:     Oriol
+Commment: https://github.com/w3c/csswg-drafts/issues/2658
+Response: https://github.com/w3c/csswg-drafts/issues/2658#issuecomment-391175246
+Closed:   Rejected
+Verified: https://github.com/w3c/csswg-drafts/issues/2658#issuecomment-393271657
+Resolved: Editorial
+---
+Issue 99.
+Summary:  Blockification of blocks should establish new FC
+From:     Oriol
+Comment:  https://github.com/w3c/csswg-drafts/issues/2673
+Open:     =WG= Discuss.
+----
+Issue 100.
+Summary:  Compute 'display: contents' on elided elements to 'none'
+From:     Emlio Álvarez
+Comment:  https://github.com/w3c/csswg-drafts/issues/2755
+Open:     =WG= Discuss.
+----