Closed Bug 194705 Opened 22 years ago Closed 22 years ago

Phoenix 20030223 crashes when using a menu on a site.

Categories

(Firefox :: General, defect)

x86
Windows 2000
defect
Not set
critical

Tracking

()

RESOLVED WORKSFORME

People

(Reporter: savagebiscuits, Assigned: bugzilla)

References

()

Details

User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.3b) Gecko/20030221 Phoenix/0.5 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.3b) Gecko/20030223 Phoenix/0.5 Phoenix 20030223 crashes when you attempt to use the menu bar to the left of the site (http://www.ams.as.ro/). This also results in the loss of the cache and its contents (not sure if this is by design, though). Works fine using Phoenix 20030221. Reproducible: Always Steps to Reproduce: 1. Go to http://www.ams.as.ro/. 2. Navigate mouse to the menu bar to the left of the site. 3. Actual Results: Phoenix 20030223 crashes and cache is lost. Expected Results: Should be able to navigate with the menu bar.
Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.3b) Gecko/20030223 crashes here too.
Keyword -> Crash please Talkback ID TB17438078H WFM with Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.3b) Gecko/20030216 and Phoenix 20030221 so this is a regression.
Just used Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.3b) Gecko/20030224 Phoenix/0.5, and it works fine now. :)
Status: UNCONFIRMED → RESOLVED
Closed: 22 years ago
Resolution: --- → FIXED
The bug is not "fixed" just because it works with the latest build. The resolution is incorrect since you reported the problem with an outdated build.
Status: RESOLVED → UNCONFIRMED
Resolution: FIXED → ---
WORKSFORME
Status: UNCONFIRMED → RESOLVED
Closed: 22 years ago22 years ago
Resolution: --- → WORKSFORME
Not totally sure what you mean, but that's probably my fault. I was referring to the 20030223 build causing a crash when using a site's menu bar, which it did, but when checked with 20030224, it worked fine. When I reported this, I was using 20030221 to do this, simply because it was the build at the time that WFM (now useing 20030224). Apologies if I misreported this.
You need to log in before you can comment on or make changes to this bug.