Fwd: Fwd: cssom - clientTop, et v

Nope, that was an accident. Is there a way to change the pref for
reply-to field, or is it fixed?

back to list ->

On Mon, Mar 10, 2008 at 1:24 PM, Anne van Kesteren <annevk@opera.com> wrote:
> Did you mean for this to go offlist?
>
>  On Mon, 10 Mar 2008 20:16:45 +0100, Garrett Smith <dhtmlkitchen@gmail.com>
>  wrote:
>
> > I see. But the paragraph you responded to was about "Undesirable
>  > Keywords". Here it is again:-
>  >
>  >>  > Why currentStyle's Keywords are Undesirable -
>  >>  > In IE and Opera, currentStyle return values are not clearly defined
>  >>  > and, in many cases, returns values that are undesirable. Such
>  >>  > undesirable values are "auto", "", "inherit", "medium", "bold" and
>  >>  > other keywords. When I get an undesirable value like "inherit", I
>  >>  > usually want the inherited value. For animation, it's not possible to
>  >>  > perform math on "inherit" -- i need a number. So I have to check the
>  >>  > parentNode, then the parentNode of the parentNode, all the way up
>  >>  > until I get a value. If the value is the keyword "red", I degrade. I
>  >>  > do not believe in sending down the wire a javascript colorKeyword ->
>  >>  > hex map. The browser should do the conversion.
>  >>
>  >>  That sounds reasonable. I've added a note about cascadedStyle.
>  >>
>  >
>  > - see? A whole paragraph about undesirable keywords. And you're
>  > response: "I added a note".
>
>  Read http://lists.w3.org/Archives/Public/www-style/2008Mar/0123.html and
>  see what block I quoted when I replied. See also what I said...
>
>
>
>  >>> But when you say "clientTop is an integer" - do you mean that it
>  >>> SHOULD be an integer, or that that's what browsers currently do?
>  >>
>  >>  It returns an integer per the IDL.
>  >
>  > I'm asking SHOULD clientTop return an integer?
>
>  Yes, per the IDL.
>
>
>
>  > Is that what the spec means by CSS Pixel?
>
>  No.
>
>
>
>  > I posted up an example that has a combination of rounding/flooring in
>  > different browsers. I did that because you defined: "A CSS Pixel is a
>  > CSS Pixel" You snipped that out. I am not sure if you understood or
>  > even read that. However, I can definitely say that ignoring large
>  > portions of my mails has been a direct source of communication
>  > breakdown in our conversations.
>
>  You seem to keep ignoring it when I say that it depends on the context.
>
>
>
>  > Which of the four browser results was expected? What is the desired
>  > result?
>
>  I don't understand this question.
>
>
>
>  > If you don't know what the expected result should be, then just say so.
>
>  I already explained several times what the expected result is.
>
>
>  --
>
>
> Anne van Kesteren
>  <http://annevankesteren.nl/>
>  <http://www.opera.com/>
>

Received on Monday, 10 March 2008 20:41:24 UTC