[webkit-dev] CSS properties vs. their JS bindings on the style object
mjs at apple.com
Thu Mar 1 14:22:25 PST 2012
I agree with Hyatt.
It's not like this behavior is especially harmful or confusing. Authors are unlikely to run into properties with hyphens in the names unless they go looking. And it can be useful if you ever want to pass around actual CSS property names by string in an API - no need to convert them to the funky camel-case format before looking it up.
So it seems more reasonable to just spec it, and it's certainly not a big enough deal to fork behavior between ports.
On Mar 1, 2012, at 12:31 PM, David Hyatt wrote:
> We shouldn't fragment WebKit engine behavior like that, especially when the feature is already being used to detect WebKit browsers (any WebKit-based browser would just be shooting itself in the foot by removing support for this). My vote would be to just spec it. If Trident and WebKit already do it, let's just spec it and then FF and Opera can implement it too.
> (hyatt at apple.com)
> On Mar 1, 2012, at 2:07 PM, Erik Arvidsson wrote:
>> How about making this a compile time flag or runtime flag so that
>> Apple Dashboard and iOS can keep it but let other users of WebKit
>> disable it?
>> On Tue, Feb 28, 2012 at 22:23, Benjamin Poulain <benjamin at webkit.org> wrote:
>>> On Tue, Feb 28, 2012 at 9:48 PM, <tomz at codeaurora.org> wrote:
>>>> Seriously, I'm not sure how to proceed on this. It does seem to be
>>>> outside the spec.
>>> Either update the spec or create a path to deprecate the "bug".
>>> Personally, this "feature" sounds like it could be useful for web
>>> developers so updating the spec might not be a bad idea.
>>> webkit-dev mailing list
>>> webkit-dev at lists.webkit.org
>> webkit-dev mailing list
>> webkit-dev at lists.webkit.org
> webkit-dev mailing list
> webkit-dev at lists.webkit.org
More information about the webkit-dev