kicking out google's image frame

[Xah Lee]

i have a problem i think only happens with OS X's Camino browser.
(which is based on FireFox engine, but Fire Fox on OS X doesn't have
this problem.)

Basically, my website has javascript code that kicks out google's frame
from their image search. However, i noticed that some pages under
Camino does not work. For example, go to:

http://images.google.com/images?q=bellagio&svnum=10&hl=en&lr=&safe=off

near bottom xahlee.org is my site. Click on that. On all browsers i've
tested in OS X (FF, Safari, Opera, OS 9 IE), it will kick out google
frame. But not so in Camino. In Camino, it turns out a blank in both
the top and bottom pane. (however, if the page is already loaded as in
Camino's cache, then the kicking works)

Any thoughts?

Xah
(e-mail address removed)
∑ http://xahlee.org/

 

[Xah Lee]

For posterity,

Someone nicked cl on irc.mozilla.org helped me to resolve this problem.

Basically, it has to do with mod_gzip from Apache. Either the server is
sending out that header while not actually compressing the content, or
that Camino just couldn't deal with whatever protocol/method mod_gzip
is supposed to do, i'm not sure which. But, if you disable mod_gzip on
your server, then things work as expected. To disable mod_gzip in
..htaccess, just add this line “mod_gzip_on noâ€

The relevant bug log may be this:
https://bugzilla.mozilla.org/show_bug.cgi?id=324363

as to why this happens in Camino and not in Firefox... i'm not sure.
According to cl, FireFox's latest source code may suffer the same
problem ...
--------------

The following opinion is not relevant to mozilla group, but as a
programer in the computing industry or as user of software, we
encounter all sort of puzzling, pesky, or painful problems every day.
May it be from the software, protocols, or programing languages and
tools. As a average user of computer, they simply give up in
frustration. As a programer, we often have to painstaking deal with a
huge mess of trial'n'error, looking of one bag of semi-documents and
specs, checking one bag of bug logs here or there, and often the source
of problem remains a mystery.

I believe a good way to resolve this situation is through Responsible
Software Licensing. Please see:
http://xahlee.org/UnixResource_dir/writ/responsible_license.html

Xah
(e-mail address removed)
∑ http://xahlee.org/