W3C home > Mailing lists > Public > www-style@w3.org > March 2012

Re: [css3-images] Remove all references to out-of-document elements and CSSElementMap?

From: Tab Atkins Jr. <jackalmage@gmail.com>
Date: Tue, 27 Mar 2012 07:40:02 -0700
Message-ID: <CAAWBYDCo-8aLof2FKTsR5_zvH-VLni7EF37pF5-kp2SBLFC7ow@mail.gmail.com>
To: robert@ocallahan.org
Cc: www-style list <www-style@w3.org>
On Tue, Mar 27, 2012 at 5:50 AM, Robert O'Callahan <robert@ocallahan.org> wrote:
> On Tue, Mar 20, 2012 at 2:18 PM, Tab Atkins Jr. <jackalmage@gmail.com>
> wrote:
>> 1. Some people don't like having id selectors refer to out-of-document
>> elements, as it's inconsistent with how the same selector would work
>> in other contexts.
>
> In the original proposal this wasn't a problem since it wasn't an ID
> selector per se, just a name that could be resolved using the dedicated
> element map or falling back to the id map.

So the fact that it looked exactly like an id selector was accidental. ^_^


>> My proposal is to drop all references to this ability for now, and
>> resolve these issues either in Images 4 or another spec like CSSOM.
>> I'd remove all references to out-of-document elements from the spec.
>> This still leaves in useful abilities, like the ability to use a
>> non-rendered element; it would just require putting the element into
>> the document and giving it display:none.
>
> Actually this does remove some power: now you can only render elements in
> the same document. Previously you could render elements in other documents,
> which has some use-cases, e.g. rendering the contents of IFRAMEs without
> clipping to the IFRAME element to make live thumbnails of Web pages.
> (Perhaps more useful in browser extensions than on the public Web.)

I know this removes some power, but not enough to cripple the feature.

~TJ
Received on Tuesday, 27 March 2012 14:40:55 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 22 May 2012 03:48:53 GMT