Re: [webkit-dev] CSS properties vs. their JS bindings on the style object

2012-03-02 Thread tomz
Thanks for all the feedback. I agree that fragmenting WebKit behavior would be a bad idea since just leaving this in has no downside other than unspec'd capability. There is a discussion of this ongoing in w3c. Ref http://lists.w3.org/Archives/Public/www-style/2012Feb/0655.html. I'll look into

Re: [webkit-dev] CSS properties vs. their JS bindings on the style object

2012-03-01 Thread Erik Arvidsson
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? erik On Tue, Feb 28, 2012 at 22:23, Benjamin Poulain benja...@webkit.org wrote: On Tue, Feb 28, 2012 at 9:48 PM,  t...@codeaurora.org wrote:

Re: [webkit-dev] CSS properties vs. their JS bindings on the style object

2012-03-01 Thread David Hyatt
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

Re: [webkit-dev] CSS properties vs. their JS bindings on the style object

2012-03-01 Thread Maciej Stachowiak
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

[webkit-dev] CSS properties vs. their JS bindings on the style object

2012-02-28 Thread Tom Zakrajsek
While investigating https://bugs.webkit.org/show_bug.cgi?id=77427, Dave and I have been trekking through the bindings code. Multiword CSS property names are hyphen-delimited and lower-case, while the equivalent JS binding names are camel-case. In the implementation, our binding code is

Re: [webkit-dev] CSS properties vs. their JS bindings on the style object

2012-02-28 Thread Simon Fraser
On Feb 28, 2012, at 5:00 PM, Tom Zakrajsek wrote: While investigating https://bugs.webkit.org/show_bug.cgi?id=77427, Dave and I have been trekking through the bindings code. Multiword CSS property names are hyphen-delimited and lower-case, while the equivalent JS binding names are

Re: [webkit-dev] CSS properties vs. their JS bindings on the style object

2012-02-28 Thread Eric Seidel
It would have to be WebKit-only content, correct? On Tue, Feb 28, 2012 at 5:04 PM, Simon Fraser simon.fra...@apple.comwrote: On Feb 28, 2012, at 5:00 PM, Tom Zakrajsek wrote: While investigating https://bugs.webkit.org/show_bug.cgi?id=77427, Dave and I have been trekking through the bindings

Re: [webkit-dev] CSS properties vs. their JS bindings on the style object

2012-02-28 Thread Simon Fraser
Yes, of which there is plenty. Simon On Feb 28, 2012, at 5:10 PM, Eric Seidel wrote: It would have to be WebKit-only content, correct? On Tue, Feb 28, 2012 at 5:04 PM, Simon Fraser simon.fra...@apple.com wrote: On Feb 28, 2012, at 5:00 PM, Tom Zakrajsek wrote: While investigating

Re: [webkit-dev] CSS properties vs. their JS bindings on the style object

2012-02-28 Thread tomz
Yeah, but how many people really use this Trident thing ;) Seriously, I'm not sure how to proceed on this. It does seem to be outside the spec. Humorously, even Microsoft's has references that imply that the script binding is named differently from the CSS attribute.

Re: [webkit-dev] CSS properties vs. their JS bindings on the style object

2012-02-28 Thread tomz
Sorry, I posted the wrong Microsoft link. Here's the one I meant ... http://msdn.microsoft.com/en-us/library/ie/ms537842%28v=vs.85%29.aspx --Tom Yeah, but how many people really use this Trident thing ;) Seriously, I'm not sure how to proceed on this. It does seem to be outside the spec.