> I wasn't reading closely enough. I see you add the div if the
> documentElement.clientWidth is not 0.Though it still has the effect of
> making the scrollHeight 1 in that document. I'm not sure why that
> is.
My detection method was actually part of another feature test looking
for the root
On 1/12/11, jdalton wrote:
> @Balázs Galambosi:
>
> I detect the scroll element in FuseJS using something similar to:
> http://dl.dropbox.com/u/513327/scrollel/quirks.html
> http://dl.dropbox.com/u/513327/scrollel/standards.html
So you add a div, set it to be 1px tall, and then remove the div
2011/1/13 jdalton :
> @Balázs Galambosi:
>
> I detect the scroll element in FuseJS using something similar to:
> http://dl.dropbox.com/u/513327/scrollel/quirks.html
> http://dl.dropbox.com/u/513327/scrollel/standards.html
>
> It seems to detect it correctly.
> If both body and docEl will report scr
On Jan 12, 5:50 pm, Balázs Galambosi wrote:
> Greetings to all!
>
> Why is it that in Chrome both standards and quirks mode uses
> document.body for scroll values?
Due to a Chrome bug described here:
http://code.google.com/p/chromium/issues/detail?id=2891
it is a very old bug and the suggeste
