John,
the report is OK and says the truth...Mexicans would say "ay ay
ay !!!".
This is something that should have been avoided...a too critical place
to play with.
The problem I see is that my patch and test for iframes got changed:
Line 2952 is currently:
if ( document.documentElement.doScroll && typeof window.frameElement
=== "undefined" ) (function(){
This will always exclude the doScroll() magic.
When does the type of that property assumes an "undefined" type ? I
would bet for "never" ?
That property can be "null" which is an "object" not an "undefined"
value. Please fix that a.s.a.p. to avoid further problems and wrong
reports.
I would take my part of responsibility for not having checked that,
but releases are so fast I didn't even know a 1.3.1 was already
available.
Diego
On 27 Gen, 17:24, John Resig <jere...@gmail.com> wrote:
> Do you have a demo page that we can look at?
>
> --John
>
> On Fri, Jan 23, 2009 at 11:01 AM, helianthus
>
> <project.heliant...@gmail.com> wrote:
>
> > 1.2.6:
> > No problems on all browsers tested.
> > 1.3.1:
> > IE7 & IE8 beta2: Fires only after all images are completely loaded.
> > FF3, Opera 9, Chrome: Fires right after DOM is loaded.
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"jQuery Development" group.
To post to this group, send email to jquery-dev@googlegroups.com
To unsubscribe from this group, send email to
jquery-dev+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/jquery-dev?hl=en
-~----------~----~----~----~------~----~------~--~---
