W3C home > Mailing lists > Public > www-style@w3.org > May 2010

Re: Selectors, vendor prefixes (again...) and IE9

From: David Hyatt <hyatt@apple.com>
Date: Mon, 17 May 2010 12:45:49 -0500
Cc: www-style list <www-style@w3.org>, Daniel Glazman <daniel.glazman@disruptive-innovations.com>
Message-id: <8FF3B76F-4010-418F-8C3E-459C0E65914D@apple.com>
To: Brad Kemper <brad.kemper@gmail.com>
On May 17, 2010, at 11:27 AM, Brad Kemper wrote:

> On May 15, 2010, at 12:24 PM, Brad Kemper wrote:
>>> It's important that if ::selection is specified, that it doesn't try to dictate a model that is incompatible with the UA's selection model.  The UA needs to have the flexibility to interpret the specified properties in a way that is compatible with its model.
>> It already is incompatible with Webkit on iPhones. Or vice versa. On iPhones and iPads, the selection area is a translucent shape in front of the page, with what appears to be an ink effect (looks like "multiply" or "darken" in Photoshop parlance, but I'm not sure; it doesn't lighten black text, but it does darken red text). That shape can select across multiple inline elements, but becomes a single rectangle when selecting across more than one block display or table-* display box. There do not appear to be any new per-element boxes inserted around the text and above the background.
> So my view on ::selection is that is is rather quaint to imagine that the visual representation of selection is something that can be adequately described via color and background-color alone. I believe Mac has been using color overlays with ink effects since the days of Quickdraw and OS 6. It is especially something distinctively different when you get to iPhone, iPads, etc. Would they be considered non-complient if ::selection was in a REC? I hope not, because I happen to think the iPad selection overlay is a better way to indicate selection, even if it was on a desktop, and I would rather be choosing the color of THAT, with its built in ink effect, or maybe even choosing the ink effect (lighten, darken, multiply, screen, etc.). 
> And it does seem rather absurd to be creating hundreds or thousands of pseudo-elements if someone does a "select all" on a desktop computer, as Hyatt pointed out. There is only ever one selection at a time anyway, usually.
> My view on prefixes in general is that CR is not PR, but a prefixed entity loses its prefix even though we all know further changes might be required. I think once an "official" implementation (non-beta, non-developer release) has shipped, then we cannot require the prefix to be put back on, but we can say that it is still changeable. In other words, it goes back to having the status of a prefixed property, even though the prefix is not there anymore.

I agree.  We're certainly willing to make changes to ::selection in WebKit, even though it is unprefixed.

Received on Monday, 17 May 2010 17:46:54 UTC

This archive was generated by hypermail 2.3.1 : Monday, 2 May 2016 14:38:35 UTC