RealTechNews.com - Independent Tech

Tuesday, November 30, 2004

Mozilla Rendering Problem?
Calling All Todds Dept: We are having some sort of weird rendering problem in Mozilla. One reader named Les sent us in a screenshot (see picture on the right)and Bill himself has reported a problem.

Bill hits refresh and it clears, but if there is anyone out there who knows their way around a template, please let us know what we can do and we'll feature you here in an upcoming and moving tribute.

# Permalink Posted at 9:21 AM 8 comments Email this Link

Comments on this Item:

Speaking of Mozilla issues, try reading the site with the Javascript console open.
---
Error: document.parentWindow has no properties
Source File: http://www.aliceandbill.com/
---

I frequently have the Venkman debugger open while working, and taking a break to browse your sight is especially painful with this error.

just add a simple:
if (document.parentWindow) before you try to reference the object.

# posted by Anonymous 9:32 AM

This resembles the appearence of, and a note relating to a "rare gzip encoding bug" that Blogger identified a while back. I experienced it myself a few times, but has disappeared for me with the latest version of Firefox.

The top of a page would be normal, and then turn to garbage part way down. A refresh would resolve it.

If that's the case, it's not your template.

# posted by Al 10:51 AM

Al,

That sounds like what I'm seeing. Thing is, I'm already on the latest version of Firefox....

Kevin.

# posted by Anonymous 12:59 PM

All I can add is that it's in the known Blogger issues list. It's been there for a while.

http://help.blogger.com/bin/answer.py?answer=791
(It's hard to spot... page search for 'gzip')

I also found a message in yahoo groups that suggests it's related to Apache and the way it handles gzip encoding, but the message had little insite.

You could bounce an email off blogger tech-support, I suppose, but they'd likely just repeat that they know of the issue.

# posted by Al 4:56 PM

On Firefox 1.0PR I saw it on the first load. Successive loads did not exhibit this bug. I'm leaning toward firefox (or supporting libs) bug.

# posted by Anonymous 11:42 AM

I have been running Firefox since the newest release came out several weeks ago. I began to experience this problem with the A & B site only about 1 week ago though. Seems like the problem might be related to a change made external to the firefox browser.

# posted by Anonymous 5:56 PM

I had been getting that problem almost every time I opened the page but I also noticed that a refresh would solve it. It hasn't happened in the past 20 minutes or so though.

# posted by David 10:11 PM

Oops, it just happened again today :(

# posted by David 9:30 AM

Post a Comment