W3C home > Mailing lists > Public > whatwg@whatwg.org > November 2011

[whatwg] Allowing custom attributes on <html> or <body> in documents for media resources

From: Tab Atkins Jr. <jackalmage@gmail.com>
Date: Tue, 15 Nov 2011 15:47:35 -0800
Message-ID: <CAAWBYDAdhtVQ+xuqhz9PchUthPWzoHYG+TzAmU2hcZ1zrenEFw@mail.gmail.com>
On Tue, Nov 15, 2011 at 3:29 PM, Robert O'Callahan <robert at ocallahan.org> wrote:
> On Wed, Nov 16, 2011 at 12:06 PM, Tab Atkins Jr. <jackalmage at gmail.com>
> wrote:
>> On Tue, Nov 15, 2011 at 2:07 PM, Robert O'Callahan <robert at ocallahan.org>
>> wrote:
>> > So I propose that a "toplevel" class be set on the root element of a
>> > media
>> > resource document in a toplevel browsing context.
>>
>> While I'd normally object that classes are purely an author extension
>> point and UAs should stay out, this is a UA-generated page in the
>> first place so it's not a big deal.
>>
>> I might suggest using a pseudoclass instead, though, as that's the
>> normal UA extension point. ?Is there any particular reason to prefer a
>> class over a pseudoclass?
>
> It's a little bit more code to implement a pseudoclass, at least in Gecko.
> (It's literally one line to add a custom class or attribute; the situation
> is probably similar in other engines.)
>
> If a custom attribute seems better to you, that's just as easy as a class.

I'm slightly happier with a custom attribute, yeah, just from a purity
standpoint.  It's equivalent otherwise.

~TJ
Received on Tuesday, 15 November 2011 15:47:35 UTC

This archive was generated by hypermail 2.4.0 : Wednesday, 22 January 2020 16:59:37 UTC