Closed Bug 424536 Opened 17 years ago Closed 15 years ago

gmail hangs "Loading..." when trying to open a message

Categories

(Firefox :: General, defect)

PowerPC
macOS
defect
Not set
normal

Tracking

()

RESOLVED INCOMPLETE

People

(Reporter: joe, Unassigned)

Details

User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.5; en-US; rv:1.9b5pre) Gecko/2008032204 Minefield/3.0b5pre Build Identifier: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.5; en-US; rv:1.9b5pre) Gecko/2008032204 Minefield/3.0b5pre Beginning with the 2008-03-21 nightly, I can no longer open mail in my Google Apps version 2 gmail account. The error console has a handful of warnings about "Error in parsing value for property 'display'. Declaration dropped." but there are no additional warnings or errors when I click on the message. Other things work, like keyboard navigation, making messages as read, and archiving them. It only appears to be opening messages that doesn't work. Reproducible: Always Steps to Reproduce: From the main mail view, click on any message. Doesn't matter if it's the recipient or the subject. Actual Results: It displays the yellow banner "Loading..." at the top of the page, but instead of ultimately (and usually quickly) displaying the message, it just sits there forever. Expected Results: After briefly displaying "Loading...", display the message. Using the proto 0.14.1 theme. I had the "Better Gmail" extension enabled, but the behavior persists with it off.
What about if you make a new firefox profile for a test? - http://kb.mozillazine.org/Profile_manager (Do not delete any existing profiles)
Version: unspecified → Trunk
It does work with a clean profile.
OK if it works with a new profile then it sounds like something is broken in your existing profile, and so this probably isn't a firefox bug.
(In reply to comment #3) > OK if it works with a new profile then it sounds like something is broken in > your existing profile, and so this probably isn't a firefox bug. It certainly sounds like something is broken in the existing profile, but I'm not convinced it isn't a bug. What in my profile would cause that Javascript to stop executing properly? What would cause it to break when it did?
Joe, still see this?
Whiteboard: [closeme 2009-12-10]
No. It's been a while, but I think I just worked around it by continuing with a new profile. Unfortunately, no good resolution on this. Feel free to close it.
Status: UNCONFIRMED → RESOLVED
Closed: 15 years ago
Resolution: --- → INCOMPLETE
Whiteboard: [closeme 2009-12-10]
You need to log in before you can comment on or make changes to this bug.