W3C home > Mailing lists > Public > www-svg@w3.org > May 2012

Re: dropping contentStyleType and contentScriptType

From: Tab Atkins Jr. <jackalmage@gmail.com>
Date: Sat, 19 May 2012 09:07:11 -0700
Message-ID: <CAAWBYDAgiFB8KB8_VvwxETkrdnzn2DYKs6sE6bXJbn4EVh5jZA@mail.gmail.com>
To: Cameron McCormack <cam@mcc.id.au>
Cc: SVG public list <www-svg@w3.org>
On Fri, May 18, 2012 at 8:00 PM, Cameron McCormack <cam@mcc.id.au> wrote:
> In SVG 1.1, the contentStyleType="" attribute can be placed on an <svg>
> element to indicate the styling language in use in any style="" attributes
> in that subtree.  The spec says:
>  Since the only widely deployed language used for inline styling (in
>  style elements and style attributes) is CSS, and since that is
>  already the default language if contentStyleType is omitted, in
>  practice contentStyleType is not well supported in user agents. XSL
>  style sheets are typically external. If a new style sheet language
>  becomes popular, it might not use style attributes and could easily
>  declare which language is in use with the type attribute on the style
>  element.
>  The use of contentStyleType is therefore deprecated; new content
>  should not use it. Future versions of the SVG specification may
>  remove contentStyleType.
> I propose we do that now.
> Similarly you can place contentScriptType="" on <svg> to indicate the
> scripting language in any event handler attributes.  There's no wording
> currently about dropping this attribute, but I have never seen anyone use it
> to specify anything other than JavaScript, and HTML also does not support a
> feature like this.  I propose we drop it too, and assume JavaScript.

Agree.  No reason to beat around the bush on these two aspects - CSS
and JS won the respective wars.

Received on Saturday, 19 May 2012 16:08:03 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 22:54:35 UTC