diff --git a/css-color-3/issues-lc-2008.html b/css-color-3/issues-lc-2008.html
index 53510aa46d4..fb3bdf37d25 100644
--- a/css-color-3/issues-lc-2008.html
+++ b/css-color-3/issues-lc-2008.html
@@ -86,12 +86,12 @@
Raised by
David Baron
- URL
+ URL
N/A
Proposed Resolution
improve index
Status
-editorial, spec edited to improve index
+editorial, spec edited to improve index
@@ -100,11 +100,11 @@
@@ -147,13 +147,13 @@
report of browser bugs from test suite
Raised by
Paul Tykodi
- URL
+ URL
http://lists.w3.org/Archives/Public/www-style/2008Jun/0023.html http://lists.w3.org/Archives/Public/www-style/2008Jun/0029.html
Proposed Resolution
-not a spec issue
+not a spec issue
Status
-not a spec issue
+not a spec issue
@@ -165,13 +165,13 @@
still confused about interaction of opacity and rgba()
Raised by
Matt Bonner
- URL
+ URL
http://lists.w3.org/Archives/Public/www-style/2008Jun/0024.html http://lists.w3.org/Archives/Public/www-style/2010Aug/0451.html
Proposed Resolution
-normative reference to SVG 1.1 simple alpha compositing
+normative reference to SVG 1.1 simple alpha compositing
Status
-spec edited
+spec edited
@@ -183,7 +183,7 @@
opacity should only apply to in-flow children, and shouldn't create a stacking context
Raised by
Andrew Fedoniuk
- URL
+ URL
http://lists.w3.org/Archives/Public/www-style/2008Jul/0139.html http://lists.w3.org/Archives/Public/www-style/2008Jul/0142.html http://lists.w3.org/Archives/Public/www-style/2008Jul/0145.html http://lists.w3.org/Archives/Public/www-style/2008Jul/0166.html http://lists.w3.org/Archives/Public/www-style/2008Jul/0167.html http://lists.w3.org/Archives/Public/www-style/2008Jul/0168.html http://lists.w3.org/Archives/Public/www-style/2008Jul/0170.html http://lists.w3.org/Archives/Public/www-style/2008Jul/0173.html http://lists.w3.org/Archives/Public/www-style/2009Feb/0244.html http://lists.w3.org/Archives/Public/www-style/2009Feb/0245.html
@@ -204,7 +204,7 @@
ICC features shouldn't be removed
Raised by
Chris Murphy
- URL
+ URL
http://lists.w3.org/Archives/Public/www-style/2008Jul/0184.html http://lists.w3.org/Archives/Public/www-style/2008Jul/0189.html http://lists.w3.org/Archives/Public/www-style/2008Jul/0191.html http://lists.w3.org/Archives/Public/www-style/2008Jul/0205.html http://lists.w3.org/Archives/Public/www-style/2008Jul/0208.html http://lists.w3.org/Archives/Public/www-style/2008Jul/0225.html http://lists.w3.org/Archives/Public/www-style/2008Jul/0230.html http://lists.w3.org/Archives/Public/www-style/2008Jul/0241.html http://lists.w3.org/Archives/Public/www-style/2008Jul/0258.html http://lists.w3.org/Archives/Public/www-style/2008Jul/0259.html http://lists.w3.org/Archives/Public/www-style/2008Jul/0278.html http://lists.w3.org/Archives/Public/www-style/2008Jul/0281.html http://lists.w3.org/Archives/Public/www-style/2008Aug/0072.html http://lists.w3.org/Archives/Public/www-style/2008Aug/0269.html http://lists.w3.org/Archives/Public/www-style/2008Aug/0270.html http://lists.w3.org/Archives/Public/www-style/2008Sep/0147.html http://lists.w3.org/Archives/Public/www-style/2008Sep/0148.html
@@ -223,13 +223,13 @@
Gamma correction section is out of date
Raised by
Chris Murphy
- URL
+ URL
http://lists.w3.org/Archives/Public/www-style/2008Jul/0185.html http://lists.w3.org/Archives/Public/www-style/2008Jul/0229.html http://lists.w3.org/Archives/Public/www-style/2008Jul/0459.html
Resolution
remove section (resolved, 2009-11-03 F2F meeting)
Status
-spec edited
+spec edited
@@ -241,7 +241,7 @@
opacity relative to multiple ancestors
Raised by
Marshal Horn
- URL
+ URL
http://lists.w3.org/Archives/Public/www-style/2008Jul/0409.html
Proposed Resolution
reject all new features (and not sure what this one means, either)
@@ -255,17 +255,17 @@
@@ -277,7 +277,7 @@
include HSL values in color tables
Raised by
David Perrell
- URL
+ URL
http://lists.w3.org/Archives/Public/www-style/2008Jul/0457.html http://lists.w3.org/Archives/Public/www-style/2008Jul/0462.html
Proposed Resolution
@@ -295,11 +295,11 @@
does HSL get mapped to the sRGB color space
Raised by
David Perrell
- URL
+ URL
http://lists.w3.org/Archives/Public/www-style/2008Jul/0458.html http://lists.w3.org/Archives/Public/www-style/2008Jul/0461.html http://lists.w3.org/Archives/Public/www-style/2008Jul/0463.html http://lists.w3.org/Archives/Public/www-style/2008Jul/0468.html http://lists.w3.org/Archives/Public/www-style/2008Jul/0472.html
Proposed Resolution 1
-no change (question already answered in spec)
+no change (question already answered in spec)
Proposed Resolution 2
add a statement with “must” in it to state the equivalence as a conformance requirement
Status
@@ -315,14 +315,14 @@
remove paragraph about clipping values outside gamut
Raised by
Chris Murphy
- URL
+ URL
http://lists.w3.org/Archives/Public/www-style/2008Jul/0459.html http://lists.w3.org/Archives/Public/www-style/2008Jul/0460.html http://lists.w3.org/Archives/Public/www-style/2008Jul/0464.html http://lists.w3.org/Archives/Public/www-style/2008Jul/0465.html http://lists.w3.org/Archives/Public/www-style/2008Jul/0466.html
Proposed Resolution
gamut clipping clarified to be to device gamut
Status
-spec edited
+spec edited
@@ -334,13 +334,13 @@
Raised by
Dave Singer
- URL
+ URL
http://lists.w3.org/Archives/Public/www-style/2008Jul/0467.html http://lists.w3.org/Archives/Public/www-style/2008Jul/0469.html
Proposed Resolution
edit section 3 accordingly to remove redundant or tautological text
Status
-spec edited - no more section 3.1.1
+spec edited - no more section 3.1.1
@@ -352,7 +352,7 @@
Raised by
Dave Singer
- URL
+ URL
http://lists.w3.org/Archives/Public/www-style/2008Jul/0467.html http://lists.w3.org/Archives/Public/www-style/2010Sep/0842.html http://lists.w3.org/Archives/Public/www-style/2010Sep/0845.html http://lists.w3.org/Archives/Public/www-style/2010Sep/0844.html http://lists.w3.org/Archives/Public/www-style/2010Sep/0850.html
Reporter's response to resolution
@@ -372,7 +372,7 @@
currentColor should not be treated as color:inherit at parse time (and color:inherit should have a space in it)
Raised by
Krzysztof Maczyński
- URL
+ URL
http://lists.w3.org/Archives/Public/www-style/2008Jul/0539.html http://lists.w3.org/Archives/Public/www-style/2008Jul/0540.html
Note
@@ -380,7 +380,7 @@
Proposed Resolution
do the additional edits to match the previous resolution
Status
-spec edited
+spec edited
@@ -389,11 +389,11 @@
- Summary
-- long list of editorial comments from XSL FO SG (excluding comment on status section, which is the next issue)
+- long list of editorial comments from XSL FO SG (excluding comment on status section, which is the next issue)
- Raised by
- Tony Graham
-- URL
+- URL
- http://lists.w3.org/Archives/Public/www-style/2008Sep/0004.html http://lists.w3.org/Archives/Public/www-style/2010Sep/0848.html http://lists.w3.org/Archives/Public/www-style/2010Sep/0849.html
- Reporter's response to resolution
- http://lists.w3.org/Archives/Public/www-style/2010Oct/0054.html
@@ -413,11 +413,11 @@
- definition of interoperable should be changed
- Raised by
- marbux (in response to Tony Graham)
-- URL
+- URL
- http://lists.w3.org/Archives/Public/www-style/2008Sep/0004.html http://lists.w3.org/Archives/Public/www-style/2008Sep/0006.html http://lists.w3.org/Archives/Public/www-style/2008Sep/0169.html http://lists.w3.org/Archives/Public/www-style/2008Sep/0173.html
- Proposed Resolution
-- no change. ignore legal trolls, or rather, escalate them to W3C legal (which Daniel has done per http://lists.w3.org/Archives/Public/www-style/2008Sep/0173.html) and let them sort it out. in the mean while, proceed with business as usual.
+- no change. ignore legal trolls, or rather, escalate them to W3C legal (which Daniel has done per http://lists.w3.org/Archives/Public/www-style/2008Sep/0173.html) and let them sort it out. in the mean while, proceed with business as usual.
- Status
- no change.
@@ -431,13 +431,13 @@
statement about advantages of HSL to RGB should not pretend to be exhaustive
Raised by
Dave Singer
-
URL
+
URL
private email to dbaron, 2008-07-28
Proposed Resolution
editorial, edit to add “Some” before “advantages”.
Status
-
spec edited
+
spec edited
@@ -449,11 +449,11 @@
need to define deprecated in a way that still requires UAs to support them (and thus need conformance requirements!)
Raised by
Rich Schwerdtfeger
- URL
+ URL
-minutes of CSS meeting, 2008-10-20, morning session: http://lists.w3.org/Archives/Public/www-style/2008Nov/0023.html
+minutes of CSS meeting, 2008-10-20, morning session: http://lists.w3.org/Archives/Public/www-style/2008Nov/0023.html
Proposed resolution
-no edit. existing definition section references CSS 2.1 definitions which defines deprecated that way.
+no edit. existing definition section references CSS 2.1 definitions which defines deprecated that way.
Status
no edit needed.
@@ -468,13 +468,13 @@
Raised by
Steve Zilles
- URL
-minutes of CSS meeting, 2008-10-20, morning session: http://lists.w3.org/Archives/Public/www-style/2008Nov/0023.html
+ URL
+minutes of CSS meeting, 2008-10-20, morning session: http://lists.w3.org/Archives/Public/www-style/2008Nov/0023.html
Proposed Resolution
do so
Status
-spec edited
+spec edited
@@ -486,13 +486,13 @@
Raised by
Krzysztof Maczyński
- URL
+ URL
http://lists.w3.org/Archives/Public/www-style/2009Mar/0097.html http://lists.w3.org/Archives/Public/www-style/2009Mar/0106.html
Proposed Resolution
editorial feedback accepted. request to not deprecate rejected.
Status
-spec edited to re-use some of the “If you want to emulate ” wording suggested in http://lists.w3.org/Archives/Public/www-style/2009Mar/0106.html
+spec edited to re-use some of the “If you want to emulate ” wording suggested in http://lists.w3.org/Archives/Public/www-style/2009Mar/0106.html
@@ -504,7 +504,7 @@
Accept angle units and allow omission of % units in hsl()
Raised by
Ludger Buenger
- URL
+ URL
http://lists.w3.org/Archives/Public/www-style/2009Jul/0154.html http://lists.w3.org/Archives/Public/www-style/2009Jul/0155.html http://lists.w3.org/Archives/Public/www-style/2009Jul/0156.html
Proposed resolution
@@ -516,17 +516,17 @@
@@ -538,7 +538,7 @@
case of currentColor is odd
Raised by
David Perrell
- URL
+ URL
http://lists.w3.org/Archives/Public/www-style/2009Aug/0313.html http://lists.w3.org/Archives/Public/www-style/2009Aug/0314.html http://lists.w3.org/Archives/Public/www-style/2009Aug/0341.html http://lists.w3.org/Archives/Public/www-style/2009Aug/0342.html http://lists.w3.org/Archives/Public/www-style/2009Aug/0355.html http://lists.w3.org/Archives/Public/www-style/2009Aug/0384.html
Proposed Resolution
@@ -550,14 +550,14 @@
- Summary
-- add mechanism for migrating to being conformant to the part of the spec that says CSS colors are in sRGB
+- add mechanism for migrating to being conformant to the part of the spec that says CSS colors are in sRGB
- Raised by
- David Baron, Beth Dakin
-- URL
+- URL
- minutes of F2F meeting, 2009-11-03 (have resolution)
- Resolution
-- updated: do this in CSS4-color instead: “RESOLUTION: re-add a 'color-correction' property with the two values 'default' and 'srgb'”, ”'default': what UA would do if the property weren't specified at all. That can change over time. (E.g., at the moment we (Safari/Webkit) don't do color managament at all. But we may do so in the future.)”, ”'srgb': All colors are presumed to be defined in the sRGB color space unless a more precise embedded profile is specified within content data. For images that do have a profile built into their data, that profile is used. For images that do not have a profile, the sRGB profile is used so that the colors in these images can be kept “in synch” with the colors specified in CSS and HTML.”
+- updated: do this in CSS4-color instead: “RESOLUTION: re-add a 'color-correction' property with the two values 'default' and 'srgb'”, ”'default': what UA would do if the property weren't specified at all. That can change over time. (E.g., at the moment we (Safari/Webkit) don't do color managament at all. But we may do so in the future.)”, ”'srgb': All colors are presumed to be defined in the sRGB color space unless a more precise embedded profile is specified within content data. For images that do have a profile built into their data, that profile is used. For images that do not have a profile, the sRGB profile is used so that the colors in these images can be kept “in synch” with the colors specified in CSS and HTML.”
- Status
- no edit in CSS3-color.
@@ -568,14 +568,14 @@
- Summary
-- should depend on CSS 2.1 instead of css3-syntax and css3-values
+- should depend on CSS 2.1 instead of css3-syntax and css3-values
- Raised by
- David Baron
- Proposed Resolution
-- normative reference to CSS 2.1, informative to css3-syntax and css3-values
+- normative reference to CSS 2.1, informative to css3-syntax and css3-values
- Status
-- spec edited
+- spec edited
@@ -588,7 +588,7 @@
- Raised by
- David Baron
-- URL
+- URL
- http://lists.w3.org/Archives/Public/www-style/2010Sep/0849.html
- Reporter's response to resolution
- http://lists.w3.org/Archives/Public/www-style/2010Oct/0053.html
@@ -596,7 +596,7 @@
- just remove the note saying otherwise
- Status
-- spec edited.
+- spec edited.
@@ -611,7 +611,7 @@
Proposed Resolution
change to 'color keyword'
Status
-editorial, spec edited
+editorial, spec edited
@@ -627,7 +627,7 @@
Reporters response to resolution
http://lists.w3.org/Archives/Public/www-style/2010Oct/0070.html
Proposed Resolution
-update them. Note: When I (Tantek) last asked Chris Lilley about what should we update the [SRGB] reference to, he said we should use the same reference as the latest SVG.
+update them. Note: When I (Tantek) last asked Chris Lilley about what should we update the [SRGB] reference to, he said we should use the same reference as the latest SVG.
From http://www.w3.org/TR/SVG/refs.html :
@@ -645,7 +645,7 @@
- Status
-- updated the shared bibliography for the CSS specs accordingly.
+- updated the shared bibliography for the CSS specs accordingly.
@@ -657,7 +657,7 @@
add CIE color specification to CSS3 color
Raised by
Alexis Shaw
- URL
+ URL
http://lists.w3.org/Archives/Public/www-style/2010Sep/0313.html http://lists.w3.org/Archives/Public/www-style/2010Sep/0330.html http://lists.w3.org/Archives/Public/www-style/2010Sep/0341.html http://lists.w3.org/Archives/Public/www-style/2010Sep/0341.html http://lists.w3.org/Archives/Public/www-style/2010Sep/0462.html (then drifted off topic) http://lists.w3.org/Archives/Public/www-style/2010Sep/0853.html
Reporter's response to resolution
@@ -677,7 +677,7 @@
HSL Tables
Raised by
Christoph Päper
- URL
+ URL
http://lists.w3.org/Archives/Public/www-style/2010Sep/0312.html
Reporter's response to resolution
@@ -698,12 +698,12 @@
Raised by
Christoph Päper
- URL
+ URL
http://lists.w3.org/Archives/Public/www-style/2010Sep/0312.html http://lists.w3.org/Archives/Public/www-style/2010Oct/0073.html
Reporter's response to resolution
Proposed Resolution
-spec is correct, no change
+spec is correct, no change
Status
no change
@@ -718,7 +718,7 @@
Raised by
Christoph Päper
- URL
+ URL
http://lists.w3.org/Archives/Public/www-style/2010Sep/0312.html
Reporter's response to resolution
http://lists.w3.org/Archives/Public/www-style/2010Oct/0077.html
@@ -738,7 +738,7 @@
CIE colorimetry
Raised by
Etan Wexler
- URL
+ URL
http://lists.w3.org/Archives/Public/www-style/2010Sep/0355.html http://lists.w3.org/Archives/Public/www-style/2010Sep/0472.html http://lists.w3.org/Archives/Public/www-style/2010Oct/0071.html
Reporter's response to resolution
diff --git a/css-gcpm-3/2009-06-10.html b/css-gcpm-3/2009-06-10.html
index 3eafb62de87..2be9bab1593 100644
--- a/css-gcpm-3/2009-06-10.html
+++ b/css-gcpm-3/2009-06-10.html
@@ -71,12 +71,12 @@ Editor's Draft 10 June 2009
Copyright © 2009 W3C® (MIT, ERCIM, W3C® (MIT, ERCIM, Keio), All Rights Reserved. W3C liability,
This specification defines in general a subset of CSS 2.1 [[!CSS21]] that is
+
This specification defines in general a subset of CSS 2.1 [[!CSS21]] that is
to be considered a baseline for interoperability between
- implementations of CSS on constrained devices (e.g. mobile phones).
- Its intent is not to produce a profile of CSS incompatible with the
+ implementations of CSS on constrained devices (e.g. mobile phones).
+ Its intent is not to produce a profile of CSS incompatible with the
complete specification, but rather to ensure that implementations
that due to platform limitations cannot support the entire
specification implement a common subset that is interoperable not
only amongst constrained implementations but also with complete
ones. Additionally, this specification aligns itself as much as
- possible with the OMA Wireless CSS 1.1 [[WCSS11]] specification. At the same
- time, OMA is doing
- alignment work in OMA Wireless CSS 1.2 [[WCSS12]]. It is aimed at aligning the
- mandatory compliance items between CSS Mobile Profile 2.0 and OMA Wireless CSS 1.2 [[WCSS12]].
+ possible with the OMA Wireless CSS 1.1 [[WCSS11]] specification. At the same
+ time, OMA is doing
+ alignment work in OMA Wireless CSS 1.2 [[WCSS12]]. It is aimed at aligning the
+ mandatory compliance items between CSS Mobile Profile 2.0 and OMA Wireless CSS 1.2 [[WCSS12]].
This profile is obsolete. Please see the latest
CSS Snapshot for the
@@ -69,7 +69,7 @@ Status text:
Introduction
-This document specifies a profile of CSS that is in general based on CSS 2.1 [[!CSS21]], but requires as well new features from CSS 3. In addition the document defines an OPTIONAL feature set, that is suggested to be implemented by more advanced user agents.
+This document specifies a profile of CSS that is in general based on CSS 2.1 [[!CSS21]], but requires as well new features from CSS 3. In addition the document defines an OPTIONAL feature set, that is suggested to be implemented by more advanced user agents.
Conformance
@@ -82,25 +82,25 @@ RFC 2119 [[!RFC2119]].
Since the goal of this specification is to define a baseline interoperability level, user
- agents MAY accept CSS documents conforming to CSS 2.1 or subsequent revisions of the CSS
+ agents MAY accept CSS documents conforming to CSS 2.1 or subsequent revisions of the CSS
family of Recommendations.
In order to conform to this specification, user agents, authoring tools, and content MUST
conform to the Conformance
and Error conditions
- section of the CSS 2.1 specification [[!CSS21]], with the following modifications.
+ section of the CSS 2.1 specification [[!CSS21]], with the following modifications.
-
Only features marked as supported in this specification are REQUIRED.
Aside of the REQUIRED feature set,
an additional OPTIONAL feature set is given, that may be implemented by more advanced user agents.
- This feature set is REQUIRED by the CDF as in [[!WICDMobile10]].
- Support for a larger set of CSS 2.1 is OPTIONAL.
+ This feature set is REQUIRED by the CDF as in [[!WICDMobile10]].
+ Support for a larger set of CSS 2.1 is OPTIONAL.
-
- The requirement concerning which CSS 2.1 media types
+ The requirement concerning which CSS 2.1 media types
are supported is tightened so that both the
handheld and all media
types MUST be accepted and processed. Other media types MAY be accepted and processed as well.
@@ -114,8 +114,8 @@ RFC 2119 [[!RFC2119]].
Selectors
Selectors are defined in the Selectors
- chapter of the CSS 2.1 specification [[!CSS21]]. The following table identifies which selector
- constructs MUST be supported amongst those defined by CSS 2.1.
+ chapter of the CSS 2.1 specification [[!CSS21]]. The following table identifies which selector
+ constructs MUST be supported amongst those defined by CSS 2.1.
@@ -198,8 +198,8 @@ RFC 2119 [[!RFC2119]].
At-rules
At-rules are defined in the at-rules
- section of the CSS 2.1 specification [[!CSS21]]. The following table identifies which at-rule
- constructs MUST be supported amongst those defined by CSS
+ section of the CSS 2.1 specification [[!CSS21]]. The following table identifies which at-rule
+ constructs MUST be supported amongst those defined by CSS
by setting the at-rule as REQUIRED in the table's last column.
Only at-rules that are part of the suggested feature set for advanced user agents are listed here as OPTIONAL.
@@ -235,19 +235,19 @@ RFC 2119 [[!RFC2119]].
Properties
- Properties are defined in several chapters of the CSS 2.1
- specification [[!CSS21]] and in case of marquee properties in the CSS Marquee Module [[!CSS3MARQUEE]]. The following table identifies which properties
+ Properties are defined in several chapters of the CSS 2.1
+ specification [[!CSS21]] and in case of marquee properties in the CSS Marquee Module [[!CSS3MARQUEE]]. The following table identifies which properties
MUST be supported amongst those defined by
- CSS by setting the property as REQUIRED in the table's last column.
+ CSS by setting the property as REQUIRED in the table's last column.
Only properties that are part of the suggested feature set for advanced user agents are listed here as OPTIONAL.
The property syntax is provided (expressed using the same value specifications
- as CSS 2.1) when it is subsetted from the original.
+ as CSS 2.1) when it is subsetted from the original.
Limitations that apply to a property apply equally to its shorthand alternative.
| Property |
- Syntax (if different from CSS) |
+ Syntax (if different from CSS) |
Conformance |
@@ -649,12 +649,12 @@ RFC 2119 [[!RFC2119]].
-
- Content Providers will reach a larger and more satisfied audience by following Mobile Web Best Practices [[MOBILE-BP]] and CSS Techniques for Web Content Accessibility Guidelines [[WCAG10-CSS-TECHS]].
+ Content Providers will reach a larger and more satisfied audience by following Mobile Web Best Practices [[MOBILE-BP]] and CSS Techniques for Web Content Accessibility Guidelines [[WCAG10-CSS-TECHS]].
-
- The OMA Wireless CSS 1.1 [[WCSS11]] introduced
+ The OMA Wireless CSS 1.1 [[WCSS11]] introduced
three extensions
Marquee, Access Keys and Input.
- Those extensions are deprecated in OMA Wireless CSS 1.2 [[WCSS12]]. The Marquee functionality has been redefined by the marquee properties of the CSS 3 box model [[!CSS3MARQUEE]]
+ Those extensions are deprecated in OMA Wireless CSS 1.2 [[WCSS12]]. The Marquee functionality has been redefined by the marquee properties of the CSS 3 box model [[!CSS3MARQUEE]]
@@ -663,7 +663,7 @@ RFC 2119 [[!RFC2119]].
A user agent MUST support all value types defined in the
Values section of the
- CSS 2.1 specification [[!CSS21]], with the following exceptions:
+ CSS 2.1 specification [[!CSS21]], with the following exceptions:
- Support for counter values is OPTIONAL
@@ -681,8 +681,8 @@ RFC 2119 [[!RFC2119]].
The editors wish to thank the authors of the previous version of this document,
Ted Wugofski (Openwave), Doug Dominiak (Openwave, formerly Motorola),
Peter Stark (Ericsson), and Tapas Roy (Openwave), as well as the authors of
- the OMA Wireless CSS specifications and the CSS 2.1 specification.
- Furthermore, the editors want to thank the CDF WG for their participation on this specification.
+ the OMA Wireless CSS specifications and the CSS 2.1 specification.
+ Furthermore, the editors want to thank the CDF WG for their participation on this specification.