Closed GoogleCodeExporter closed 8 years ago
And what is the solution if it's solveable ?
Original comment by alex.cologne
on 30 Jul 2011 at 1:34
"The issue has been resolved by imgZoom 0.2.1. What was going on is that the
script was using an image's offsetWidth property in a handler to the image's
'load' event. Somehow the presence of any beforeload event listener delays the
setting of offsetWidth to just after the handler is called (as can be seen
using a setTimeout of 0 milliseconds), but it is not set within the handler
(i.e. equals 0). Since the spec does not require .offsetWidth to be set when
the 'load' event is fired (the image's .width property has this purpose and
works correctly), this behavior seems legit, although the fact that it happens
exclusively with beforeload listeners indicates that it might be the
consequence of another bug."
It was solved with imgZoom.
I'm using #shDisplay {top:1% !important;) as a temp fix but it doesn't look
that good: http://ingasjodin.se/?p=tavlor
And the controls isn't fixed.
Original comment by anteu...@gmail.com
on 30 Jul 2011 at 1:37
So I'm testing some modifications of:
if ( ! t.Top ) {
if ( window.pageYOffset != 0 ) t.Top = window.pageYOffset;
else t.Top = (document.documentElement.scrollTop > 0) ? document.documentElement.scrollTop : document.body.scrollTop;
}
Original comment by anteu...@gmail.com
on 30 Jul 2011 at 1:41
Maybe this should be a similar issue as reported in issue #381
Original comment by alex.cologne
on 30 Jul 2011 at 1:49
Thanks I will try that! Brb
Original comment by anteu...@gmail.com
on 30 Jul 2011 at 1:50
http://ingasjodin.se/?p=tavlor
There it didn't do it. Buttons still screwed and that is still with the 1% fix.
Original comment by anteu...@gmail.com
on 30 Jul 2011 at 2:13
Until somebody give me a hint where to look, I will close this as I see no
failure at my side
Original comment by alex.cologne
on 14 Aug 2011 at 6:38
This is the error when I have latest Google Chrome Beta and Adblock Plus Beta.
Original comment by anteu...@gmail.com
on 14 Aug 2011 at 11:10
Attachments:
I have tracked this error, it's a WebKit problem. This has now been committed
and I can confirm that Google Chrome beta (16) no longer displays this issue,
and I imagine Safari will follow suit.
Cheers
Russ
Original comment by russtar...@gmail.com
on 20 Nov 2011 at 5:08
Ah yes looking good now, thanks!
Original comment by anteu...@gmail.com
on 20 Nov 2011 at 5:51
Original issue reported on code.google.com by
anteu...@gmail.com
on 30 Jul 2011 at 1:14