[media-types] Re: Review request for updated registration of text/css

Chris Lilley <[email protected]> Thu, 26 Mar 2026 18:50:15 -0400
Newsgroups gmane.ietf.types
Message-ID <[email protected]>
The new template (with public.css added):

Type name: text

Subtype name: css

Required parameters: none

Optional parameters: charset (but see below)

Encoding considerations:

   For use with transports that are not 8-bit clean, quoted-
   printable encoding is recommended since the majority of
   characters will be CSS syntax and thus correspond to the
   US-ASCII-compatible subrange of UTF-8.

Security considerations:

   CSS is a modular specification and thus, the individual
   Security Considerations section of each CSS module in use
   should be consulted.

Interoperability considerations:

   CSS has proven to be widely interoperable across computer
   platforms, across Web browsers of different makes, and for import
   and export in multiple authoring tools.

Published specification:

   https://www.w3.org/TR/css

Applications that use this media type:

   CSS is device-, platform- and vendor-neutral and is supported by
   a wide range of Web user agents and authoring tools for
   formatting HTML documents.

Fragment identifier considerations:

   N/A

Additional information:

   Deprecated alias names for this type: N/A
   Magic number(s): N/A
   File extension(s): .css
   macOS Uniform Type Identifier(s): public.css
   Windows clipboard name(s): N/A

Person & email address to contact for further information:

   The W3C CSS Working Group<[email protected]>

Intended usage:

   COMMON

Restrictions on usage:

   N/A

Author: The W3C CSS Working Group

Change controller: W3C

Fallback encoding:

   For Web compatibility, to determine the character encoding,
   user agents follow the CSS Syntax Level 3 specification,
   "To determine the fallback encoding of a stylesheet"
   https://www.w3.org/TR/css-syntax-3/#determine-the-fallback-encoding

   Stylesheet authors should author their stylesheets in UTF-8, and
   ensure that either an HTTP header (or equivalent method) declares
   the encoding of the stylesheet to be UTF-8, or that the referring
   document declares its encoding to be UTF-8.

-- 
Chris Lilley
@[email protected]
W3C Distinguished Expert, Color, Graphics & Fonts
W3C Technical Programming Team, Core Web Design

_______________________________________________
media-types mailing list -- [email protected]
To unsubscribe send an email to [email protected]