- From: Vincent Hardy via cvs-syncmail <cvsmail@w3.org>
- Date: Fri, 16 Dec 2011 19:11:22 +0000
- To: public-css-commits@w3.org
Update of /sources/public/csswg/css3-regions
In directory hutz:/tmp/cvs-serv14166
Modified Files:
Overview.html Overview.src.html alternate-spec-style.css
Log Message:
Updated prototype style a bit. Removed divs with class set to 'issues moved', 'issue stale' or 'issue resolved'. Removed last pseudo-code selectors. Moved issues to now point to bugzilla entries.
Index: Overview.html
===================================================================
RCS file: /sources/public/csswg/css3-regions/Overview.html,v
retrieving revision 1.35
retrieving revision 1.36
diff -u -d -r1.35 -r1.36
--- Overview.html 29 Nov 2011 04:28:32 -0000 1.35
+++ Overview.html 16 Dec 2011 19:11:20 -0000 1.36
@@ -64,27 +64,35 @@
margin-bottom: 0.5em;
}
+ #mobile-logo {
+ display: none;
+ }
+
</style>
<link href="http://www.w3.org/StyleSheets/TR/W3C-ED.css" rel=stylesheet
type="text/css">
<link href=alternate-spec-style.css id=st rel=stylesheet
- title="additional spec styles" type="text/css">
+ title="alternate spec style" type="text/css">
<body>
- <div class=head id=div-head> <!--begin-logo-->
+ <div class=head id=div-head>
+ <p><a href="http://www.w3.org/"><img alt=W3C height=53 id=mobile-logo
+ src="http://www.w3.org/2008/site/images/logo-w3c-mobile-lg" width=90></a>
+ <!--begin-logo-->
+
<p><a href="http://www.w3.org/"><img alt=W3C height=48
src="http://www.w3.org/Icons/w3c_home" width=72></a> <!--end-logo--></p>
<h1 id=css-regions-module>CSS Regions Module Level 3</h1>
- <h2 class="no-num no-toc" id=longstatus-date>Editor's Draft 29 November
+ <h2 class="no-num no-toc" id=longstatus-date>Editor's Draft 16 December
2011</h2>
<dl>
<dt>This version:
<dd><a
- href="http://www.w3.org/TR/2011/ED-css3-regions-20111129/">http://www.w3.org/csswg/css3-regions</a>
+ href="http://www.w3.org/TR/2011/ED-css3-regions-20111216/">http://www.w3.org/csswg/css3-regions</a>
<dt>Latest version:
@@ -275,6 +283,9 @@
<li><a href="#changes"><span class=secno>10. </span>Changes</a>
<ul class=toc>
<li><a href="#changes_from_June_09_2011"><span class=secno>10.1.
+ </span>Changes from November 29<sup>th</sup> 2011 version</a>
+
+ <li><a href="#changes_from_June_09_2011"><span class=secno>10.2.
</span>Changes from June 09<sup>th</sup> 2011 version</a>
</ul>
@@ -491,15 +502,6 @@
flow</em></a> (see the ‘<a href="#flow-from"><code
class=property>flow-from</code></a>’ property).
- <div class="issue moved">
- <p>See <a
- href="http://wiki.csswg.org/spec/css3-regions#issue-2-auto-sizing-of-regions"></a></p>
- .
- <p>There was a recent discussion on intrinsic sizing of regions which <a
- href="http://lists.w3.org/Archives/Public/www-style/2011Jun/0629.html">has
- not been resolved</a></p>
- .</div>
-
<h3 id=named-flow><span class=secno>2.2. </span>Named flow</h3>
<p>A <dfn id=named-flow0>named flow</dfn> is the ordered sequence of
@@ -707,7 +709,7 @@
region and associates it with a named flow.
<div class=issue-marker><a
- href="http://wiki.csswg.org/spec/css3-regions#issue-12should-we-allow-multi-column-elements-to-be-regions">Issue-12</a></div>
+ href="https://www.w3.org/Bugs/Public/show_bug.cgi?id=15191">Bug-15191</a></div>
<table class=propdef summary="flow-from property definition">
<tbody>
@@ -814,7 +816,7 @@
visually.</div>
<div class=issue-marker><a
- href="http://wiki.csswg.org/spec/css3-regions#issue-23should-regions-be-non-breakable">Issue-23</a></div>
+ href="https://www.w3.org/Bugs/Public/show_bug.cgi?id=15189">Bug-15189</a></div>
<p><span title=region>Regions</span> create a new <a
href="http://www.w3.org/TR/CSS2/visuren.html#z-index">stacking
@@ -1306,7 +1308,7 @@
<p>Only a limited list of properties can be set in a region style rule:
<div class=issue-marker><a
- href="http://wiki.csswg.org/spec/css3-regions#issue-20list-of-region-style-properties">Issue-20</a></div>
+ href="https://www.w3.org/Bugs/Public/show_bug.cgi?id=15190">Bug-15190</a></div>
<ol>
<li><a href="http://www.w3.org/TR/CSS2/fonts.html">font properties</a>
@@ -1380,18 +1382,18 @@
<strong>flow-into: article_flow;</strong>
}
- <region1_sel>, <region2_sel> {
+ #region1, #region2 {
<strong>flow-from: article_flow;</strong>
}
- /* region style RSA */
- <strong>@region <region1_sel>, <region2_sel></strong> {
+ /* region style "RSA" */
+ <strong>@region #region1, #region2</strong> {
div {...}
p {...}
}
- /* region style RSB */
- <strong>@region <region1_sel></strong> {
+ /* region style "RSB" */
+ <strong>@region #region1</strong> {
p {...}
}
@@ -1402,6 +1404,8 @@
<p id="p_2">...</p>
</div>
+<div id="region1"></div>
+<div id="region2"></div>
</pre>
@@ -1455,21 +1459,6 @@
class=html>region_1</code> is styled with this rule.</p>
</div>
- <div class="issue stale">
- <p>Making issue stale because this issue has not been raised on the
- mailing list and we will wait for implementation feedback. Is the
- proposed restriction that elements are only selected selector in a rule
- set appearing in an @region rule sufficient?
- </div>
-
- <div class="issue moved"> <a
- href="http://wiki.csswg.org/spec/css3-regions#issue-14region-lines-pseudo-selector">Moved
- to specification Wiki</a>. There is <a
- href="http://lists.w3.org/Archives/Public/www-style/2011May/0518.html">concern</a>
- that the ‘<code class=css>first-line</code>’ precedent is
- underspecified and that more specification is needed in addition to
- referencing the existing precedent.</div>
-
<p>The specificity of the selectors in a ‘<code
class=css>@region</code>’ rule is calculated as <a
href="http://www.w3.org/TR/css3-selectors/#specificity">defined</a> in the
@@ -1702,18 +1691,6 @@
regions that are document elements and not to regions that are
pseudo-elements.</div>
- <div class="issue resolved">
- <p><a
- href="http://www.w3.org/Style/CSS/Tracker/actions/350">ACTION-350</a> was
- created to add the API to the specification draft.</p>
-
- <p>It has been <a
- href="http://lists.w3.org/Archives/Public/www-style/2011May/0379.html">suggested</a>
- to add an API to find which region displays an element in a named flow.
- Should we add such an API? How would it work in a ‘<code
- class=property>multi-view</code>’ context as suggested by Alex.</p>
- </div>
-
<h3 id=region-flow-layout-events><span class=secno>6.3. </span>Region flow
layout events</h3>
@@ -1805,6 +1782,22 @@
<h2 id=changes><span class=secno>10. </span>Changes</h2>
<h3 id="changes_from_June_09_2011"><span class=secno>10.1. </span>Changes
+ from <a
+ href="http://www.w3.org/TR/2011/WD-css3-regions-20111129/">November
+ 29<sup>th</sup> 2011</a> version</h3>
+
+ <ul>
+ <li>Modified region styling examples to use element selector instead of of
+ pseudo-code selectors (this had been omitted in the previous pass at
+ removing pseudo-code from the examples).
+
+ <li>Removed divs with class set to "issue moved", "issue stale" and "issue
+ resolved" since these divs where not displayed.
+
+ <li>Minor updates to the alternate stylesheet.
+ </ul>
+
+ <h3 id="changes_from_June_09_2011"><span class=secno>10.2. </span>Changes
from <a href="http://www.w3.org/TR/2011/WD-css3-regions-20110609/">June
09<sup>th</sup> 2011</a> version</h3>
@@ -2153,21 +2146,21 @@
<dt id=CSS3-EXCLUSIONS>[CSS3-EXCLUSIONS]
- <dd>Vincent Hardy. <a
- href="http://dev.w3.org/csswg/css3-exclusions/"><cite>CSS Exclusions
- Module.</cite></a> Proposal for a CSS module. (Retrieved 15 November
- 2011) URL: <a
- href="http://dev.w3.org/csswg/css3-exclusions/">http://dev.w3.org/csswg/css3-exclusions/</a>
+ <dd>Vincent Hardy; Rossen Atanassov. <a
+ href="http://www.w3.org/TR/2011/WD-css3-exclusions-20111213/"><cite>CSS
+ Exclusions and Shapes Module Level 3.</cite></a> 13 December 2011. W3C
+ Working Draft. (Work in progress.) URL: <a
+ href="http://www.w3.org/TR/2011/WD-css3-exclusions-20111213/">http://www.w3.org/TR/2011/WD-css3-exclusions-20111213/</a>
</dd>
<!---->
<dt id=CSS3-FLEXBOX>[CSS3-FLEXBOX]
<dd>Tab Atkins Jr.; Alex Mogilevsky; L. David Baron. <a
- href="http://www.w3.org/TR/2011/WD-css3-flexbox-20110322/"><cite>Flexible
- Box Layout Module.</cite></a> 22 March 2011. W3C Working Draft. (Work in
- progress.) URL: <a
- href="http://www.w3.org/TR/2011/WD-css3-flexbox-20110322/">http://www.w3.org/TR/2011/WD-css3-flexbox-20110322/</a>
+ href="http://www.w3.org/TR/2011/WD-css3-flexbox-20111129/"><cite>CSS
+ Flexible Box Layout Module.</cite></a> 29 November 2011. W3C Working
+ Draft. (Work in progress.) URL: <a
+ href="http://www.w3.org/TR/2011/WD-css3-flexbox-20111129/">http://www.w3.org/TR/2011/WD-css3-flexbox-20111129/</a>
</dd>
<!---->
Index: alternate-spec-style.css
===================================================================
RCS file: /sources/public/csswg/css3-regions/alternate-spec-style.css,v
retrieving revision 1.16
retrieving revision 1.17
diff -u -d -r1.16 -r1.17
--- alternate-spec-style.css 29 Nov 2011 04:28:32 -0000 1.16
+++ alternate-spec-style.css 16 Dec 2011 19:11:20 -0000 1.17
@@ -1,9 +1,36 @@
body {
font-family: 'DroidSerifRegular', 'Droid Serif', serif;
font-size: 14px;
- max-width: 38em;
color: #2f2f2f;
line-height: 1.7em;
+ padding-left: 8em;
+}
+
+img[alt='W3C'] {
+ display: none;
+}
+
+#mobile-logo {
+ display: block;
+ border-radius: 0.2em;
+ box-shadow: 0.1em 0.1em 0.2em rgba(0, 0, 0, 0.2);
+}
+
+@media screen and (min-width: 68em){
+ body {
+ max-width: 50em;
+ }
+
+ #mobile-logo {
+ width: 90px;
+ height: 53px;
+ position: absolute;
+ margin-left: -120px;
+ }
+
+ img[alt='W3C'] {
+ display: none;
+ }
}
h1, h2, h3, h4, h5, h6 {
@@ -344,22 +371,6 @@
min-width: 28ex;
}
-#div-head > h1:before {
- content: '';
- background-image: url(http://www.w3.org/2008/site/images/logo-w3c-mobile-lg);
- display: block;
- width: 90px;
- height: 53px;
- position: absolute;
- margin-left: -120px;
- border-radius: 0.2em;
- box-shadow: 0.1em 0.1em 0.2em rgba(0, 0, 0, 0.2);
-}
-
-img[alt='W3C'] {
- display: none;
-}
-
.issue-marker {
@@ -371,4 +382,6 @@
.issue-marker a {
color: #c00;
+ background: none;
+ font-weight: normal;
}
\ No newline at end of file
Index: Overview.src.html
===================================================================
RCS file: /sources/public/csswg/css3-regions/Overview.src.html,v
retrieving revision 1.40
retrieving revision 1.41
diff -u -d -r1.40 -r1.41
--- Overview.src.html 29 Nov 2011 04:28:32 -0000 1.40
+++ Overview.src.html 16 Dec 2011 19:11:20 -0000 1.41
@@ -67,22 +67,30 @@
margin-bottom: 0.5em;
}
+ #mobile-logo {
+ display: none;
+ }
+
</style>
<link rel="stylesheet" type="text/css"
href="http://www.w3.org/StyleSheets/TR/W3C-ED.css">
<link id="st" href="alternate-spec-style.css" rel="stylesheet"
- type="text/css" title="additional spec styles">
+ type="text/css" title="alternate spec style">
</head>
<body>
<div class="head" id="div-head">
+ <p><a href="http://www.w3.org/"><img id="mobile-logo" alt="W3C" height="53" src=
+ "http://www.w3.org/2008/site/images/logo-w3c-mobile-lg" width="90"></a>
+
+
<!--begin-logo-->
- <p><a href="http://www.w3.org/"><img alt="W3C" height="48" src=
+ <p><a href="http://www.w3.org/"><img id="logo" alt="W3C" height="48" src=
"http://www.w3.org/Icons/w3c_home" width="72"></a> <!--end-logo--></p>
<h1 id="css-regions-module">CSS Regions Module Level 3</h1>
@@ -341,12 +349,6 @@
box</a> and has an associated <em>named flow</em> (see the 'flow-from'
property).</p>
- <div class="issue moved">
- <p>See <a href="http://wiki.csswg.org/spec/css3-regions#issue-2-auto-sizing-of-regions"></a></p>.
- <p>There was a recent discussion on intrinsic sizing of regions which
- <a href="http://lists.w3.org/Archives/Public/www-style/2011Jun/0629.html">has not been resolved</a></p>.
- </div>
-
<h3 id="named-flow">Named flow</h3>
<p>A <dfn>named flow</dfn> is the ordered sequence of elements
@@ -521,7 +523,7 @@
<h3 id="the-flow-from-property">The 'flow-from' property</h3>
<p>The 'flow-from' property makes an element a region and associates it with a named flow.</p>
- <div class="issue-marker"><a href="http://wiki.csswg.org/spec/css3-regions#issue-12should-we-allow-multi-column-elements-to-be-regions">Issue-12</a></div>
+ <div class="issue-marker"><a href="https://www.w3.org/Bugs/Public/show_bug.cgi?id=15191">Bug-15191</a></div>
<table class="propdef" summary="flow-from property definition">
<tr>
@@ -624,7 +626,7 @@
are not formatted visually.
</div>
- <div class="issue-marker"><a href="http://wiki.csswg.org/spec/css3-regions#issue-23should-regions-be-non-breakable">Issue-23</a></div>
+ <div class="issue-marker"><a href="https://www.w3.org/Bugs/Public/show_bug.cgi?id=15189">Bug-15189</a></div>
<p><span title="region">Regions</span> create a new <a href="http://www.w3.org/TR/CSS2/visuren.html#z-index">stacking context</a>. <span title="region">Regions</span> establish a new <a href="http://www.w3.org/TR/CSS2/visuren.html#block-formatting">block formatting Context</a>.</p>
@@ -1116,7 +1118,7 @@
selectors found in the style rule.</p>
<p>Only a limited list of properties can be set in a region style rule:</p>
- <div class="issue-marker"><a href="http://wiki.csswg.org/spec/css3-regions#issue-20list-of-region-style-properties">Issue-20</a></div>
+ <div class="issue-marker"><a href="https://www.w3.org/Bugs/Public/show_bug.cgi?id=15190">Bug-15190</a></div>
<ol>
<li><a href="http://www.w3.org/TR/CSS2/fonts.html">font properties</a></li>
@@ -1149,18 +1151,18 @@
<strong>flow-into: article_flow;</strong>
}
- <region1_sel>, <region2_sel> {
+ #region1, #region2 {
<strong>flow-from: article_flow;</strong>
}
- /* region style RSA */
- <strong>@region <region1_sel>, <region2_sel></strong> {
+ /* region style "RSA" */
+ <strong>@region #region1, #region2</strong> {
div {...}
p {...}
}
- /* region style RSB */
- <strong>@region <region1_sel></strong> {
+ /* region style "RSB" */
+ <strong>@region #region1</strong> {
p {...}
}
@@ -1171,6 +1173,8 @@
<p id="p_2">...</p>
</div>
+<div id="region1"></div>
+<div id="region2"></div>
</pre>
@@ -1224,22 +1228,6 @@
</div>
- <div class="issue stale">
- <p>Making issue stale because this issue has not been raised on the
- mailing list and we will wait for implementation feedback.
-
- Is the proposed restriction that elements are only selected selector in
- a rule set appearing in an @region rule sufficient?
- </div>
-
- <div class="issue moved">
- <a href="http://wiki.csswg.org/spec/css3-regions#issue-14region-lines-pseudo-selector">Moved to specification Wiki</a>.
- There is <a href=
- "http://lists.w3.org/Archives/Public/www-style/2011May/0518.html">concern</a>
- that the ''first-line'' precedent is underspecified and that more
- specification is needed in addition to referencing the existing
- precedent.
- </div>
<p>The specificity of the selectors in a '@region' rule is calculated as
<a href="http://www.w3.org/TR/css3-selectors/#specificity">defined</a> in
@@ -1432,16 +1420,6 @@
The Element interface extension is only available to regions that are
document elements and not to regions that are pseudo-elements.
</div>
-
- <div class="issue resolved">
- <p><a href="http://www.w3.org/Style/CSS/Tracker/actions/350">ACTION-350</a> was created
- to add the API to the specification draft.</p>
- <p>It has been <a href=
- "http://lists.w3.org/Archives/Public/www-style/2011May/0379.html">suggested</a>
- to add an API to find which region displays an element in a named flow.
- Should we add such an API? How would it work in a 'multi-view' context
- as suggested by Alex.</p>
- </div>
<h3 id="region-flow-layout-events">Region flow layout events</h3>
@@ -1497,6 +1475,16 @@
<h2 id="changes">Changes</h2>
+ <h3 id="changes_from_June_09_2011">Changes from <a href="http://www.w3.org/TR/2011/WD-css3-regions-20111129/">November 29<sup>th</sup> 2011</a> version</h3>
+
+ <ul>
+ <li>Modified region styling examples to use element selector instead of of pseudo-code selectors (this had been omitted in the
+ previous pass at removing pseudo-code from the examples).</li>
+ <li>Removed divs with class set to "issue moved", "issue stale" and "issue resolved" since these divs where not displayed.
+ <li>Minor updates to the alternate stylesheet.</li>
+ </ul>
+
+
<h3 id="changes_from_June_09_2011">Changes from <a href="http://www.w3.org/TR/2011/WD-css3-regions-20110609/">June 09<sup>th</sup> 2011</a> version</h3>
<ul>
Received on Friday, 16 December 2011 19:11:29 UTC