5858 </ style >
5959
6060
61+ < meta content ="Bikeshed 1.0.0 " name ="generator ">
6162 < style >
6263 table .source-demo-pair {
6364 width : 100% ;
@@ -200,7 +201,13 @@ <h2 class="no-num no-toc no-ref heading settled" id="subtitle"><span class="cont
200201
201202 < div data-fill-with ="warning "> </ div >
202203
203- < p class ="copyright " data-fill-with ="copyright "> < a href ="http://www.w3.org/Consortium/Legal/ipr-notice#Copyright "> Copyright</ a > © 2015 < a href ="http://www.w3.org/ "> < abbr title ="World Wide Web Consortium "> W3C</ abbr > </ a > < sup > ®</ sup > (< a href ="http://www.csail.mit.edu/ "> < abbr title ="Massachusetts Institute of Technology "> MIT</ abbr > </ a > , < a href ="http://www.ercim.eu/ "> < abbr title ="European Research Consortium for Informatics and Mathematics "> ERCIM</ abbr > </ a > , < a href ="http://www.keio.ac.jp/ "> Keio</ a > , < a href ="http://ev.buaa.edu.cn/ "> Beihang</ a > ), All Rights Reserved. W3C < a href ="http://www.w3.org/Consortium/Legal/ipr-notice#Legal_Disclaimer "> liability</ a > , < a href ="http://www.w3.org/Consortium/Legal/ipr-notice#W3C_Trademarks "> trademark</ a > and < a href ="http://www.w3.org/Consortium/Legal/copyright-documents "> document use</ a > rules apply.
204+ < p class ="copyright " data-fill-with ="copyright "> < a href ="http://www.w3.org/Consortium/Legal/ipr-notice#Copyright "> Copyright</ a > © 2015 < a href ="http://www.w3.org/ ">
205+ < acronym title ="World Wide Web Consortium "> W3C</ acronym >
206+ </ a > < sup > ®</ sup > (< a href ="http://www.csail.mit.edu/ ">
207+ < acronym title ="Massachusetts Institute of Technology "> MIT</ acronym >
208+ </ a > , < a href ="http://www.ercim.eu/ ">
209+ < acronym title ="European Research Consortium for Informatics and Mathematics "> ERCIM</ acronym >
210+ </ a > , < a href ="http://www.keio.ac.jp/ "> Keio</ a > , < a href ="http://ev.buaa.edu.cn/ "> Beihang</ a > ). W3C < a href ="http://www.w3.org/Consortium/Legal/ipr-notice#Legal_Disclaimer "> liability</ a > , < a href ="http://www.w3.org/Consortium/Legal/ipr-notice#W3C_Trademarks "> trademark</ a > and < a href ="http://www.w3.org/Consortium/Legal/copyright-documents "> document use</ a > rules apply.
204211</ p >
205212
206213 < hr title ="Separator for header ">
@@ -254,7 +261,7 @@ <h2 class="no-num no-toc no-ref heading settled" id="status"><span class="conten
254261
255262</ p >
256263 < p >
257- This document is governed by the < a href ="http://www.w3.org/2014/Process-20140801/ "> 1 August 2014 W3C Process Document</ a > .
264+ This document is governed by the < a href ="http://www.w3.org/2014/Process-20140801/ " id =" w3c_process_revision " > 1 August 2014 W3C Process Document</ a > .
258265
259266</ p >
260267 < p >
@@ -287,7 +294,7 @@ <h2 class="no-num no-toc no-ref heading settled" id="contents"><span class="cont
287294 < li > < a href ="#style-of-fragments "> < span class ="secno "> 6.1.2</ span > < span class ="content "> Styling of fragments</ span > </ a >
288295 < li > < a href ="#style-in-fragments "> < span class ="secno "> 6.1.3</ span > < span class ="content "> Styling inside fragments</ span > </ a >
289296 </ ul >
290- < li > < a href ="#max-lines "> < span class ="secno "> 6.2</ span > < span class ="content "> The < span class ="property " title ="max-lines "> max-lines</ span > property</ span > </ a >
297+ < li > < a href ="#max-lines "> < span class ="secno "> 6.2</ span > < span class ="content "> The < span class ="property " data-lt ="max-lines "> max-lines</ span > property</ span > </ a >
291298 </ ul >
292299 < li > < a href ="#static-media "> < span class ="secno "> 7</ span > < span class ="content "> Overflow in static media</ span > </ a >
293300 < li > < a href ="#acknowledgments "> < span class ="secno "> </ span > < span class ="content ">
@@ -475,7 +482,7 @@ <h3 class="heading settled" data-level="2.2" id="scrollable-overflow"><span clas
475482 </ p >
476483
477484
478- < p class ="issue " id ="issue-36f1a23e "> < a class ="self-link " href ="#issue-36f1a23e "> </ a >
485+ < p class ="issue " id ="issue-6b232bb5 "> < a class ="self-link " href ="#issue-6b232bb5 "> </ a >
479486 The following definition should be rewritten to use
480487 the concept of < a href ="http://dev.w3.org/csswg/css-transforms/#3d-rendering-context "> 3D rendering context</ a > < a data-link-type ="biblio " href ="#biblio-css3-transforms "> [CSS3-TRANSFORMS]</ a >
481488 and related terms,
@@ -486,7 +493,7 @@ <h3 class="heading settled" data-level="2.2" id="scrollable-overflow"><span clas
486493
487494 < p >
488495 Given the following definitions
489- < span class ="issue " id ="issue-172bf444 "> < a class ="self-link " href ="#issue-172bf444 "> </ a > which belong in < a data-link-type ="biblio " href ="#biblio-css3-transforms "> [CSS3-TRANSFORMS]</ a > </ span > :
496+ < span class ="issue " id ="issue-101a26b2 "> < a class ="self-link " href ="#issue-101a26b2 "> </ a > which belong in < a data-link-type ="biblio " href ="#biblio-css3-transforms "> [CSS3-TRANSFORMS]</ a > </ span > :
490497 </ p >
491498
492499
@@ -829,7 +836,7 @@ <h2 class="heading settled" data-level="3" id="overflow-properties"><span class=
829836 </ div >
830837
831838
832- < p class ="issue " id ="issue-45d3d9aa "> < a class ="self-link " href ="#issue-45d3d9aa "> </ a >
839+ < p class ="issue " id ="issue-74b71fcd "> < a class ="self-link " href ="#issue-74b71fcd "> </ a >
833840 Are all 4 of the < span class ="css "> paged-*</ span > values really needed?
834841 </ p >
835842
@@ -843,7 +850,7 @@ <h2 class="heading settled" data-level="3" id="overflow-properties"><span class=
843850 </ p >
844851
845852
846- < p class ="issue " id ="issue-2c53acbd "> < a class ="self-link " href ="#issue-2c53acbd "> </ a >
853+ < p class ="issue " id ="issue-52e2a181 "> < a class ="self-link " href ="#issue-52e2a181 "> </ a >
847854 < a data-link-type ="biblio " href ="#biblio-css3-marquee "> [CSS3-MARQUEE]</ a > describes an < a class ="property " data-link-type ="propdesc " href ="http://www.w3.org/TR/2008/CR-css3-marquee-20081205/#the-overflow-style "> overflow-style</ a > property,
848855 but it has not picked up implementation experience
849856 that the working group is aware of.
@@ -869,7 +876,7 @@ <h2 class="heading settled" data-level="3" id="overflow-properties"><span class=
869876 < h2 class ="heading settled " data-level ="4 " id ="scrolling-overflow "> < span class ="secno "> 4. </ span > < span class ="content "> Scrolling and hidden overflow</ span > < a class ="self-link " href ="#scrolling-overflow "> </ a > </ h2 >
870877
871878
872- < p class ="issue " id ="issue-726ed205 "> < a class ="self-link " href ="#issue-726ed205 "> </ a >
879+ < p class ="issue " id ="issue-75945e26 "> < a class ="self-link " href ="#issue-75945e26 "> </ a >
873880 Move material from < a data-link-type ="biblio " href ="#biblio-css21 "> [CSS21]</ a > and < a data-link-type ="biblio " href ="#biblio-css3box "> [CSS3BOX]</ a > here.
874881 </ p >
875882
@@ -884,14 +891,14 @@ <h2 class="heading settled" data-level="4" id="scrolling-overflow"><span class="
884891 < h2 class ="heading settled " data-level ="5 " id ="paginated-overflow "> < span class ="secno "> 5. </ span > < span class ="content "> Paginated overflow</ span > < a class ="self-link " href ="#paginated-overflow "> </ a > </ h2 >
885892
886893
887- < p class ="issue " id ="issue-03349ce5 "> < a class ="self-link " href ="#issue-03349ce5 "> </ a > overflow:paginate or overflow:pages (or paged-x, paged-y, paged-x-controls, paged-y-controls as < a data-link-type ="biblio " href ="#biblio-css3gcpm "> [CSS3GCPM]</ a > has?)</ p >
894+ < p class ="issue " id ="issue-0a5e0b64 "> < a class ="self-link " href ="#issue-0a5e0b64 "> </ a > overflow:paginate or overflow:pages (or paged-x, paged-y, paged-x-controls, paged-y-controls as < a data-link-type ="biblio " href ="#biblio-css3gcpm "> [CSS3GCPM]</ a > has?)</ p >
888895
889896
890897 < p class ="issue " id ="issue-22961e25 "> < a class ="self-link " href ="#issue-22961e25 "> </ a > Ability to display N pages at once
891898rather than just one page at once?</ p >
892899
893900
894- < p class ="issue " id ="issue-7328bc11 "> < a class ="self-link " href ="#issue-7328bc11 "> </ a >
901+ < p class ="issue " id ="issue-1f266e7d "> < a class ="self-link " href ="#issue-1f266e7d "> </ a >
895902 The current implementation of paginated overflow uses
896903 the < a class ="property " data-link-type ="propdesc " href ="#propdef-overflow "> overflow</ a > /< a class ="property " data-link-type ="propdesc " href ="#propdef-overflow-x "> overflow-x</ a > /< a class ="property " data-link-type ="propdesc " href ="#propdef-overflow-y "> overflow-y</ a > properties
897904 rather than the < a class ="property " data-link-type ="propdesc " href ="http://www.w3.org/TR/2008/CR-css3-marquee-20081205/#the-overflow-style "> overflow-style</ a > property as proposed
@@ -952,7 +959,7 @@ <h2 class="heading settled" data-level="6" id="fragment-overflow"><span class="s
952959 </ p >
953960
954961
955- < p class ="issue " id ="issue-89a60b9c "> < a class ="self-link " href ="#issue-89a60b9c "> </ a >
962+ < p class ="issue " id ="issue-c4f3aedb "> < a class ="self-link " href ="#issue-c4f3aedb "> </ a >
956963 What if we want to be able to style the pieces of an element
957964 split within another type of fragmentation context?
958965 These rules prevent ever using < a class ="css " data-link-type ="maybe " href ="#selectordef-nth-fragment "> ::nth-fragment()</ a > for that,
@@ -1008,15 +1015,15 @@ <h2 class="heading settled" data-level="6" id="fragment-overflow"><span class="s
10081015 </ div >
10091016
10101017
1011- < p class ="issue " id ="issue-f590932f "> < a class ="self-link " href ="#issue-f590932f "> </ a >
1018+ < p class ="issue " id ="issue-7c2776be "> < a class ="self-link " href ="#issue-7c2776be "> </ a >
10121019 We should specify that < a class ="css " data-link-type ="propdesc " href ="#propdef-overflow "> overflow: fragments</ a > does not apply
10131020 to at least some table parts,
10141021 and perhaps other elements as well.
10151022 We need to determine exactly which ones.
10161023 </ p >
10171024
10181025
1019- < p class ="issue " id ="issue-54f95309 "> < a class ="self-link " href ="#issue-54f95309 "> </ a >
1026+ < p class ="issue " id ="issue-6c1669e3 "> < a class ="self-link " href ="#issue-6c1669e3 "> </ a >
10201027 This specification needs to say which type of
10211028 fragmentation context is created
10221029 so that it’s clear which values of the < a class ="property " data-link-type ="propdesc "> break-*</ a > properties
@@ -1025,7 +1032,7 @@ <h2 class="heading settled" data-level="6" id="fragment-overflow"><span class="s
10251032 </ p >
10261033
10271034
1028- < p class ="issue " id ="issue-e784096c "> < a class ="self-link " href ="#issue-e784096c "> </ a >
1035+ < p class ="issue " id ="issue-08d6a80e "> < a class ="self-link " href ="#issue-08d6a80e "> </ a >
10291036 This specification needs a processing model
10301037 that will apply in cases where the layout containing the
10311038 fragments has characteristics that use the intrinsic size of the fragments
@@ -1067,7 +1074,7 @@ <h4 class="heading settled" data-level="6.1.1" id="fragment-pseudo-element"><spa
10671074 </ p >
10681075
10691076
1070- < p class ="issue " id ="issue-4cfde272 "> < a class ="self-link " href ="#issue-4cfde272 "> </ a >
1077+ < p class ="issue " id ="issue-0e3bec77 "> < a class ="self-link " href ="#issue-0e3bec77 "> </ a >
10711078 Depending on future discussions,
10721079 this < span class ="css "> ::nth-fragment(an+b)</ span > syntax
10731080 may be replaced with
@@ -1231,9 +1238,9 @@ <h4 class="heading settled" data-level="6.1.2" id="style-of-fragments"><span cla
12311238 </ p >
12321239
12331240
1234- < p class ="issue " id ="issue-20d2a9e8 "> < a class ="self-link " href ="#issue-20d2a9e8 "> </ a >
1241+ < p class ="issue " id ="issue-d95b27f9 "> < a class ="self-link " href ="#issue-d95b27f9 "> </ a >
12351242 This inheritance rule allows specifying styles indirectly
1236- (by using explicit < a class ="css " data-link-type ="maybe " href ="http://dev.w3.org/csswg/css-cascade-3/#valuedef -inherit "> inherit</ a > or using default inheritance
1243+ (by using explicit < a class ="css " data-link-type ="maybe " href ="http://dev.w3.org/csswg/css-cascade-3/#valdef-all -inherit "> inherit</ a > or using default inheritance
12371244 on properties that don’t apply to < span class ="css "> ::first-letter</ span > )
12381245 that can’t be specified directly
12391246 (based on the rules in the next section).
@@ -1772,7 +1779,7 @@ <h3 class="no-num heading settled" id="normative"><span class="content">Normativ
17721779 < dt id ="biblio-select "> < a class ="self-link " href ="#biblio-select "> </ a > [SELECT]
17731780 < dd > Tantek Çelik; et al. < a href ="http://www.w3.org/TR/2011/REC-css3-selectors-20110929/ "> Selectors Level 3</ a > . 29 September 2011. W3C Recommendation. URL: < a href ="http://www.w3.org/TR/2011/REC-css3-selectors-20110929/ "> http://www.w3.org/TR/2011/REC-css3-selectors-20110929/</ a >
17741781 < dt id ="biblio-css3-break "> < a class ="self-link " href ="#biblio-css3-break "> </ a > [css3-break]
1775- < dd > Rossen Atanassov; Elika Etemad. < a href ="http://www.w3.org/TR/css3-break/ "> CSS Fragmentation Module Level 3</ a > . 16 January 2014 . WD. URL: < a href ="http://www.w3.org/TR/css3-break/ "> http://www.w3.org/TR/css3-break/</ a >
1782+ < dd > Rossen Atanassov; Elika Etemad. < a href ="http://www.w3.org/TR/css3-break/ "> CSS Fragmentation Module Level 3</ a > . 29 January 2015 . WD. URL: < a href ="http://www.w3.org/TR/css3-break/ "> http://www.w3.org/TR/css3-break/</ a >
17761783 < dt id ="biblio-rfc2119 "> < a class ="self-link " href ="#biblio-rfc2119 "> </ a > [rfc2119]
17771784 < dd > S. Bradner. < a href ="https://tools.ietf.org/html/rfc2119 "> Key words for use in RFCs to Indicate Requirement Levels</ a > . March 1997. Best Current Practice. URL: < a href ="https://tools.ietf.org/html/rfc2119 "> https://tools.ietf.org/html/rfc2119</ a >
17781785 </ dl >
@@ -1903,8 +1910,8 @@ <h2 class="no-num heading settled" id="issues-index"><span class="content">Issue
19031910 and related terms,
19041911 particularly once those concepts stabilize following changes
19051912 proposed in the CSS WG meeting on the morning of 2014-01-28.
1906- < a href ="#issue-36f1a23e "> ↵ </ a > </ div >
1907- < div class ="issue "> which belong in < a data-link-type ="biblio " href ="#biblio-css3-transforms "> [CSS3-TRANSFORMS]</ a > < a href ="#issue-172bf444 "> ↵ </ a > </ div >
1913+ < a href ="#issue-6b232bb5 "> ↵ </ a > </ div >
1914+ < div class ="issue "> which belong in < a data-link-type ="biblio " href ="#biblio-css3-transforms "> [CSS3-TRANSFORMS]</ a > < a href ="#issue-101a26b2 "> ↵ </ a > </ div >
19081915 < div class ="issue "> undefined concept!< a href ="#issue-1b139c15 "> ↵ </ a > </ div >
19091916 < div class ="issue "> undefined term!< a href ="#issue-2d1dc4f9 "> ↵ </ a > </ div >
19101917 < div class ="issue "> MORE HERE!< a href ="#issue-75780f3f "> ↵ </ a > </ div >
@@ -1930,7 +1937,7 @@ <h2 class="no-num heading settled" id="issues-index"><span class="content">Issue
19301937 < a href ="#issue-42ea3c29 "> ↵ </ a > </ div >
19311938 < div class ="issue ">
19321939 Are all 4 of the < span class ="css "> paged-*</ span > values really needed?
1933- < a href ="#issue-45d3d9aa "> ↵ </ a > </ div >
1940+ < a href ="#issue-74b71fcd "> ↵ </ a > </ div >
19341941 < div class ="issue "> Is this the right behavior?< a href ="#issue-ef127061 "> ↵ </ a > </ div >
19351942 < div class ="issue "> Give example.< a href ="#issue-78cdbe9b "> ↵ </ a > </ div >
19361943 < div class ="issue ">
@@ -1942,7 +1949,7 @@ <h2 class="no-num heading settled" id="issues-index"><span class="content">Issue
19421949 and attempt to revive it,
19431950 despite that implementations have implemented
19441951 < a class ="property " data-link-type ="propdesc " href ="#propdef-overflow-x "> overflow-x</ a > and < a class ="property " data-link-type ="propdesc " href ="#propdef-overflow-y "> overflow-y</ a > instead?
1945- < a href ="#issue-2c53acbd "> ↵ </ a > </ div >
1952+ < a href ="#issue-52e2a181 "> ↵ </ a > </ div >
19461953 < div class ="issue ">
19471954 There are < a href ="http://lists.w3.org/Archives/Public/www-style/2012May/1197.html "> discussions</ a >
19481955 about how overflow, overflow-style, overflow-x and overflow-y
@@ -1954,13 +1961,13 @@ <h2 class="no-num heading settled" id="issues-index"><span class="content">Issue
19541961 < a href ="#issue-a8b88d7e "> ↵ </ a > </ div >
19551962 < div class ="issue ">
19561963 Move material from < a data-link-type ="biblio " href ="#biblio-css21 "> [CSS21]</ a > and < a data-link-type ="biblio " href ="#biblio-css3box "> [CSS3BOX]</ a > here.
1957- < a href ="#issue-726ed205 "> ↵ </ a > </ div >
1964+ < a href ="#issue-75945e26 "> ↵ </ a > </ div >
19581965 < div class ="issue ">
19591966 Explain which directions allow scrolling and which don’t,
19601967 as a function of < a class ="property " data-link-type ="propdesc " href ="http://dev.w3.org/csswg/css-writing-modes-3/#propdef-direction "> direction</ a >
19611968 (including propagation of < a class ="property " data-link-type ="propdesc " href ="http://dev.w3.org/csswg/css-writing-modes-3/#propdef-direction "> direction</ a > to the ICB).
19621969 < a href ="#issue-c318b1c1 "> ↵ </ a > </ div >
1963- < div class ="issue "> overflow:paginate or overflow:pages (or paged-x, paged-y, paged-x-controls, paged-y-controls as < a data-link-type ="biblio " href ="#biblio-css3gcpm "> [CSS3GCPM]</ a > has?)< a href ="#issue-03349ce5 "> ↵ </ a > </ div >
1970+ < div class ="issue "> overflow:paginate or overflow:pages (or paged-x, paged-y, paged-x-controls, paged-y-controls as < a data-link-type ="biblio " href ="#biblio-css3gcpm "> [CSS3GCPM]</ a > has?)< a href ="#issue-0a5e0b64 "> ↵ </ a > </ div >
19641971 < div class ="issue "> Ability to display N pages at once
19651972rather than just one page at once?< a href ="#issue-22961e25 "> ↵ </ a > </ div >
19661973 < div class ="issue ">
@@ -1971,7 +1978,7 @@ <h2 class="no-num heading settled" id="issues-index"><span class="content">Issue
19711978 (which also matches the < a data-link-type ="biblio " href ="#biblio-css3-marquee "> [CSS3-MARQUEE]</ a > proposal).
19721979 We should probably switch away from < a class ="property " data-link-type ="propdesc " href ="http://www.w3.org/TR/2008/CR-css3-marquee-20081205/#the-overflow-style "> overflow-style</ a > ,
19731980 but that’s not 100% clear.
1974- < a href ="#issue-7328bc11 "> ↵ </ a > </ div >
1981+ < a href ="#issue-1f266e7d "> ↵ </ a > </ div >
19751982 < div class ="issue "> Or is it as though it’s a next sibling of
19761983 the element? Need to figure out exactly how this interacts with
19771984 other box-level fixup.< a href ="#issue-74f423ed "> ↵ </ a > </ div >
@@ -1986,20 +1993,20 @@ <h2 class="no-num heading settled" id="issues-index"><span class="content">Issue
19861993 split within another type of fragmentation context?
19871994 These rules prevent ever using < a class ="css " data-link-type ="maybe " href ="#selectordef-nth-fragment "> ::nth-fragment()</ a > for that,
19881995 despite that the name seems the most logical name for such a feature.
1989- < a href ="#issue-89a60b9c "> ↵ </ a > </ div >
1996+ < a href ="#issue-c4f3aedb "> ↵ </ a > </ div >
19901997 < div class ="issue ">
19911998 We should specify that < a class ="css " data-link-type ="propdesc " href ="#propdef-overflow "> overflow: fragments</ a > does not apply
19921999 to at least some table parts,
19932000 and perhaps other elements as well.
19942001 We need to determine exactly which ones.
1995- < a href ="#issue-f590932f "> ↵ </ a > </ div >
2002+ < a href ="#issue-7c2776be "> ↵ </ a > </ div >
19962003 < div class ="issue ">
19972004 This specification needs to say which type of
19982005 fragmentation context is created
19992006 so that it’s clear which values of the < a class ="property " data-link-type ="propdesc "> break-*</ a > properties
20002007 cause breaks within this context.
20012008 We probably want < span class ="css "> break-*: region</ span > to apply.
2002- < a href ="#issue-54f95309 "> ↵ </ a > </ div >
2009+ < a href ="#issue-6c1669e3 "> ↵ </ a > </ div >
20032010 < div class ="issue ">
20042011 This specification needs a processing model
20052012 that will apply in cases where the layout containing the
@@ -2011,13 +2018,13 @@ <h2 class="no-num heading settled" id="issues-index"><span class="content">Issue
20112018 and the work done on a model there,
20122019 and the editors of that specification,
20132020 should inform what happens in this specification.
2014- < a href ="#issue-e784096c "> ↵ </ a > </ div >
2021+ < a href ="#issue-08d6a80e "> ↵ </ a > </ div >
20152022 < div class ="issue ">
20162023 Depending on future discussions,
20172024 this < span class ="css "> ::nth-fragment(an+b)</ span > syntax
20182025 may be replaced with
20192026 the new < span class ="css "> ::fragment:nth(an+b)</ span > syntax.
2020- < a href ="#issue-4cfde272 "> ↵ </ a > </ div >
2027+ < a href ="#issue-0e3bec77 "> ↵ </ a > </ div >
20212028 < div class ="issue ">
20222029 Should this apply to fragment overflow only,
20232030 or also to paginated overflow?
@@ -2036,14 +2043,14 @@ <h2 class="no-num heading settled" id="issues-index"><span class="content">Issue
20362043 having < a class ="property " data-link-type ="propdesc " href ="http://dev.w3.org/csswg/css-display-3/#propdef-display-inside "> display-inside</ a > and < a class ="property " data-link-type ="propdesc " href ="http://dev.w3.org/csswg/css-display-3/#propdef-display-outside "> display-outside</ a > specified.< a href ="#issue-d98e732d "> ↵ </ a > </ div >
20372044 < div class ="issue ">
20382045 This inheritance rule allows specifying styles indirectly
2039- (by using explicit < a class ="css " data-link-type ="maybe " href ="http://dev.w3.org/csswg/css-cascade-3/#valuedef -inherit "> inherit</ a > or using default inheritance
2046+ (by using explicit < a class ="css " data-link-type ="maybe " href ="http://dev.w3.org/csswg/css-cascade-3/#valdef-all -inherit "> inherit</ a > or using default inheritance
20402047 on properties that don’t apply to < span class ="css "> ::first-letter</ span > )
20412048 that can’t be specified directly
20422049 (based on the rules in the next section).
20432050 This is a problem.
20442051 The restrictions that apply to styling inside fragments
20452052 should also apply to inheritance from fragments.
2046- < a href ="#issue-20d2a9e8 "> ↵ </ a > </ div >
2053+ < a href ="#issue-d95b27f9 "> ↵ </ a > </ div >
20472054 < div class ="issue ">
20482055 Should this apply to fragment overflow only,
20492056 or also to paginated overflow,
0 commit comments