- From: David Hyatt <hyatt@apple.com>
- Date: Sat, 15 May 2010 01:20:21 -0500
- To: Daniel Glazman <daniel.glazman@disruptive-innovations.com>
- Cc: www-style list <www-style@w3.org>
@variables never shipped in any actual product. ::selection did. There's a big difference. What's in nightly builds is irrelevant. What matters is the syntax between shipping builds of Safari or Chrome. We have the flexibility to drop or change syntax in nightly builds as long as we haven't shipped it yet. That is in fact the whole reason I disabled @variables... fear that shipping it would lock us into supporting it forever (when the WG clearly had no consensus on behavior/syntax for the feature). dave (hyatt@apple.com) On May 15, 2010, at 1:14 AM, Daniel Glazman wrote: > Le 15/05/10 00:38, David Hyatt a écrit : > >> The problem is once something is shipped with no vendor prefix, the genie is out of the bottle. We can't then ship a new version that breaks a feature that people may have come to rely upon. It's also not realistic to expect to wait until PR to drop the vendor prefixes. It's also not realistic to expect the vendor to put the prefix back onto the property after shipping a version with no prefix. > > @variables is number one request from users and you removed it from > WebKit w/o problem. Compared to that, ::selection is hyper-minor and was > preserved. > > </Daniel> >
Received on Saturday, 15 May 2010 06:20:55 UTC