Blocking/crashing in IE 7/8
Robert Wohleb
users see blocking for a lot more than a couple of seconds. Some users
actually have IE crash. This completely goes away when the FB JS is no
longer included in the site. When the FB JS is included, but
$.fancybox() is not actually ever called, we still see the issue. Any
ideas?
We are using:
jQuery 1.3.2
Fancybox 1.3.1
JFK
Robert Wohleb
any link?
--
You received this message because you are subscribed to the Google Groups "fancybox" group.
To post to this group, send email to fanc...@googlegroups.com.
To unsubscribe from this group, send email to fancybox+u...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/fancybox?hl=en.
JFK
spiced quirks mode
On Mar 17, 1:34 pm, Robert Wohleb <rwoh...@gmail.com> wrote:
> Unfortunately no link at the moment. FB is disabled on the live site, and
> the dev server doesn't give external access. I'm going to try and condense
> the issue down to the fewest possible components so that I have a good test
> case. I wanted to ping this list first in case someone has seen something
> similar.
>
> ~Rob
>
> On Wed, Mar 17, 2010 at 1:18 PM, JFK <jfk.d...@gmail.com> wrote:
> > any link?
>
> > On Mar 17, 11:56 am, Robert Wohleb <rwoh...@gmail.com> wrote:
> > > We are seeing IE7/8 blocking for a few seconds on page load. Some
> > > users see blocking for a lot more than a couple of seconds. Some users
> > > actually have IE crash. This completely goes away when the FB JS is no
> > > longer included in the site. When the FB JS is included, but
> > > $.fancybox() is not actually ever called, we still see the issue. Any
> > > ideas?
>
> > > We are using:
> > > jQuery 1.3.2
> > > Fancybox 1.3.1
>
> > --
> > You received this message because you are subscribed to the Google Groups
> > "fancybox" group.
> > To post to this group, send email to fanc...@googlegroups.com.
> > To unsubscribe from this group, send email to
> > fancybox+u...@googlegroups.com<fancybox%2Bunsu...@googlegroups.com>
µseless
the css filters.
Even with the path's fixed it's very slow because its seem to download
the images secuentially instead with some kind of thread parallelism,
and during the downloading time of the relative images of the filters
the browser seems to block from user input.
2010/3/17 Robert Wohleb <xx...@gmail.com>
I assume you are referring to m post on "Blocking/crashing in IE
7/8". Your post came through without any thread attached.
I was also thinking that it was an issue with the IE alpha
filters. I haven't had a chance to do much testing in this direction
yet. As it is, I hadn't even fixed the relative paths for those
filters.
~Rob
On Wed, Mar 17, 2010 at 3:13 PM, µseless <yyy...@gmail.com> wrote:
i think im having the same problem.
The context in wich this problems shows its when you are
runing ie7/8
(probably 6 also) and you have disabled the cache and/or its
the first
time the fancybox.css its loaded.
It happens that the css have a couple of weird rules that make
the ie
preload images one secuentially and in this moment the
browsers doesnt
respond to the cursor in the viewer or even in the toolbar.
solution: remove this rules:
filter:
progid:DXImageTransform.Microsoft.AlphaImageLoader(src='.......
consequences: i dont really know
123gotoandplay
I am having the same issue and i have made a thread:
do you use firebug's addon ySlow?? if you do, do you get this message
as well.
The IE-proprietary AlphaImageLoader filter attempts to fix a problem
with semi-transparent true color PNG files in IE versions less than
Version 7. However, this filter blocks rendering and freezes the
browser while the image is being downloaded. Additionally, it
increases memory consumption. The problem is further multiplied
because it is applied per element, not per image.
I really hope this can be fixed
regards
On 18 mrt, 01:02, µseless <mauricioprad...@gmail.com> wrote:
> Yes, i mistake sending the comment. But i think the problem came from
> the css filters.
> Even with the path's fixed it's very slow because its seem to download
> the images secuentially instead with some kind of thread parallelism,
> and during the downloading time of the relative images of the filters
> the browser seems to block from user input.
>
> 2010/3/17 Robert Wohleb <x...@gmail.com>
> > actually haveIEcrash. This completely goes away when the FB JS is no
feastofvermin
is:
1. Open the file jquery.fancybox-1.3.1.css and remove everything at
the bottom right after the line that reads /* IE */
2. Paste this code into a new file. (We'll call it
jquery.fancybox-1.3.1-iefix.css)
3. Make the new css included dynamically on the onload event of your
page only if the browser is IE. Here's how I did it:
jQuery(function($) {
if($.fn.fancybox) {
var fbonstart = ($('.fancybox-ie').length != 0) ? function(){if($
('#fbiecssfix').length == 0) $('head').append('<link id="fbiecssfix"
rel="stylesheet" type="text/css" media="all" href="path/to/your/file/
jquery.fancybox-1.3.1-iefix.css" />');} : null;
$("#yourfancyboxlink").fancybox({'onStart': fbonstart});
}
});
Basically the class .fancybox-ie is added by fancybox only if the
browser is IE, so we can rely on this to know if fancybox needs the IE
png fix. Make sure the above code is included AFTER fancybox,
otherwise it may not work. You're obviously gonna need to change the
parts "path/to/your/file/jquery.fancybox-1.3.1-iefix.css" and
"#yourfancyboxlink".
To the developer (If you ever read this): This is very nasty problem
that affects every page on which fancybox is included under all
versions if IE. In my opinion, it makes fancybox completely unusable
on IE. I created this workaround because I really like fancybox, but
for future versions, I think a better approach would be to entirely
drop the document.load call and have all the necessary elements load
the first time fancybox is called. Sure the first call would then be a
bit slower but I think it's much more convenient than having the page
hang at load time.
Cheers!
On Mar 23, 2:56 am, 123gotoandplay <wesweatyous...@gmail.com> wrote:
> did you find a good solution?
>
> I am having the same issue and i have made a thread:
>
> do you use firebug's addon ySlow?? if you do, do you get this message
> as well.
>
> with semi-transparent true color PNG files inIEversions less than
You received this message because you are subscribed to the Google Groups "fancybox" group.
To post to this group, send email to fanc...@googlegroups.com.
