patch for 'cssFloat'

[David Hyatt]

On Oct 1, 2003, at 4:34 PM, Dirk Mueller wrote:

> On Wednesday 01 October 2003 22:34, David Hyatt wrote:
>
>> I also added support for mapping "-khtml-" properties so that they
>> could be set/retrieved from JS.  If you guys are still using "-konq-",
>> watch out for that code and do what you think is best.
>
> This amazes me. Why would you want to make our internal properties 
> available
> via Javascript?
>

In our tree, -khtml- has been used to denote both internal properties 
(like flow-mode) but also CSS3 properties (like opacity).  I have 
thought about using a different vendor prefix for the experimental 
properties vs. the internal properties.  That would solve this problem. 
  Suggestions?

(However, given that the internal KHTML properties are usable from 
author sheets anyway, unless you're going to restrict that too, 
exposing them to script seems like a minor issue.)

> Has this been a customer request? Is a realword webpage using Safari 
> internal
> CSS properties?
>

In order to do dynamic fade effects using opacity, you need to be able 
to set it from script.  Mozilla currently uses -moz-opacity, and they 
allow the setting via mozOpacity.

This also allows me to test new CSS3 experimental properties in a 
dynamic setting to ensure that they're working properly.

I hope this clears things up.  I understand that you haven't yet seen a 
WebCore with any of the experimental CSS3 properties included, so from 
your perspective, -khtml- only referred to internal properties.

dave
(hyatt at apple.com)