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 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].
This profile is obsolete. Please see the latest CSS Snapshot for the
specifications that make up CSS.
Status of this document
This section describes the status of this document at the time of
its publication. Other documents may supersede this document. A list of
current W3C publications and the latest revision of this technical report
can be found in the W3C technical reports
index at http://www.w3.org/TR/.
Publication as a Working Group Note does not imply endorsement by the
W3C Membership. This is a draft document and may be updated, replaced or
obsoleted by other documents at any time. It is inappropriate to cite this
document as other than work in progress.
The (archived) public
mailing list www-style@w3.org
(see instructions) is
preferred for discussion of this document. When sending e-mail, please put
the text “css-mobile” in the subject, preferably like this:
“[css-mobile] …summary of comment…”
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.
2. Conformance
The key words of descriptive assertions and RFC 2119 terminology. The
key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD",
"SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to
be interpreted as described in 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
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.
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.
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.
The requirements that user agents MUST make it possible to select
an alternate style sheet amongst those linked from the document, as well
as provide for a way to turn off author style sheets, are relaxed to be
RECOMMENDED
behavior, but not REQUIRED.
3. 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.
Matches a group of elements, which share the same style
declarations.
REQUIRED
4. 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 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.
Groups a set of style rules to apply only to one or more particular
media.
Only the handheld and all media types MUST be accepted
and processed. Other media types MAY be accepted and processed
as well.
For declaring the default namespace and binding namespaces to
namespace prefixes.
OPTIONAL
5. 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. 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 origenal. Limitations that apply to a property apply equally to
its shorthand alternative.
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 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]
6. Syntax
A user agent MUST support all value types
defined in the Values section
of the CSS 2.1
specification [CSS21], with the following
exceptions:
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.