Closed Bug 258862 Opened 20 years ago Closed 20 years ago

[AltSS] Crash when choosing alternate stylesheet

Categories

(Firefox :: General, defect)

defect
Not set
critical

Tracking

()

VERIFIED DUPLICATE of bug 231776

People

(Reporter: uriber, Assigned: bugzilla)

References

()

Details

Attachments

(2 files)

User-Agent:       Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; rv:1.7.3) Gecko/20040910 Firefox/0.10
Build Identifier: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; rv:1.7.3) Gecko/20040910 Firefox/0.10

Trying to choose the "orange" stylesheet on Hixie's blog (http://ln.hixie.ch)
crashes firefox. This happens both when selecting the alternate stylesheet from
the status bar, or from View > Page Style.

Reproducible: Always
Steps to Reproduce:
1. Go to http://ln.hixie.ch
2. Select View > Page Style > Orange


Actual Results:  
Firefox pauses for a few seconds, then crashes.


Talckback crash ID: TB780754Y
Mozilla/5.0 (Windows; U; Windows NT 5.0; rv:1.7.3) Gecko/20040910 Firefox/0.10 

WFM
Confirming crash.

Mozilla/5.0 (Windows; U; Windows NT 5.1; rv:1.7.3) Gecko/20040910 Firefox/0.10
->All
->NEW
Status: UNCONFIRMED → NEW
Ever confirmed: true
OS: MacOS X → All
Reproduced this with Mozilla/5.0 (Windows; U; Win98; en-US; rv:1.7)
Gecko/20040626 Firefox/0.9.1
So this is not new.
Hardware: Macintosh → All
My Talkback ID: TB782064E

Firefox certainly shouldn't crash under these circumstances, but I'm not
entirely sure how it should react either. How does it know what to look for when
the stylesheet location is ambiguous (i.e. a directory rather than a full path)?

I wouldn't recommend bandaiding this, since it's an extremely unlikely to be
discovered crash. 

Just a thought... is this bug present on the trunk? If not, we should WONTFIX
this bug (IMO) and wait until the post-1.0 Branch/Trunk merge to automatically
fix it. Can someone please add the talkback IDs to the status whiteboard? Thanks.
Minimal testcase. Please notice that if the same CSS file is the primary
stylesheet, there is no crash.
(In reply to comment #5)
> Firefox certainly shouldn't crash under these circumstances, but I'm not
> entirely sure how it should react either. How does it know what to look for when
> the stylesheet location is ambiguous (i.e. a directory rather than a full path)?

I don't think this has anything to do with the stylesheet location, but rather
with its content.
Please seem my testcase, in which the stylesheet location is specified as an
absolute URL.

> Please seem my testcase, in which the stylesheet location is specified as an
> absolute URL.

You are correct, my mistake. The problem also occurs when doing this locally
with your minimal testcase.
This also crashes the suite: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US;
rv:1.7.2) Gecko/20040803

Looks like a dupe of Bug 231776
Yes, this is a duplicate (darn! I thought I finally found a good bug!)
More specifically, see bug 229263 (which was closed as a dupe of 231776).

*** This bug has been marked as a duplicate of 231776 ***
Status: NEW → RESOLVED
Closed: 20 years ago
Resolution: --- → DUPLICATE
v
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: