Closed Bug 234305 Opened 22 years ago Closed 22 years ago

Crash if a JPEG as stylesheet and not iso-8859-1 as charset

Categories

(Firefox :: General, defect)

x86
Windows XP
defect
Not set
critical

Tracking

()

RESOLVED WORKSFORME

People

(Reporter: sooda, Assigned: bugzilla)

References

()

Details

(Keywords: crash)

User-Agent: Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.6) Gecko/20040206 Firefox/0.8 Firefox for win32 crashes if a JPEG image file is used as a style sheet. In my test case, the image is called "crash.css" and the server is giving text/css as the content type. However, the crash does not occur if iso-8859-1 (used by default) is used as the charset. Others, e.g. iso-8859-15 and utf-8 make Firefox crash. Reproducible: Always Steps to Reproduce: 1. Make a page with a JPEG as the stylesheet. 2. Make the page use e.g. iso-8859-15 or utf-8. 3. Visit the page. Actual Results: Firefox crashed. Expected Results: The page should have been displayed normally -- of course without styles since the CSS file wasn't valid. This only happens on win32. Mozilla Application Suite doesn't seem to crash, so the issue is only Firefox-specific.
Works for me Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7a) Gecko/20040217 Firefox/0.8.0+ Can you try making a fresh profile and seeing if the crash still occurs? http://texturizer.net/firefox/bugs.html#s1
Keywords: crash
(In reply to comment #1) > Can you try making a fresh profile and seeing if the crash still occurs? > http://texturizer.net/firefox/bugs.html#s1 Yes, it does. The profile doesn't seem to make any difference here.
I tried the newest trunk build and this seems to have been fixed there.
Status: UNCONFIRMED → RESOLVED
Closed: 22 years ago
Resolution: --- → FIXED
Fixed means there was a change made to the code for this bug. There was not. Reopening and resolving worksforme.
Status: RESOLVED → UNCONFIRMED
Resolution: FIXED → ---
Status: UNCONFIRMED → RESOLVED
Closed: 22 years ago22 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.