Closed Bug 12261 Opened 20 years ago Closed 20 years ago

Crash occurs whenever prefs window tries to use unicode

Categories

(Core :: Localization, defect, P1)

All
Other
defect

Tracking

()

VERIFIED INVALID

People

(Reporter: fergus, Assigned: fergus)

References

Details

A crash occurs whenever seamonkey tries to open a prefs .dtd file where a unicode character is included in the entity value.

Observed on Mac & Win, multiple pref-*.dtd files, buildID 19990813**
changing the qa contact to fergus
changing priority to p1 because...
changing severity to critical.  it will become a blocker if not fixed.

don't believe rchen should own this, it should be PrefUI owner.  Can someone confirm and change?

This bug is very similar to 11724
Priority: P3 → P1
QA Contact: teruko → fergus
Assignee: rchen → nisheeth
Is this a dup of 11724? Reassigning to nisheeth
Don't think it's a dupe, different area of functionality, but looks like one

nisheeth all the same.
Assignee: nisheeth → matt
Reassigning this to Matt Fisher who owns preferences.

One current theory is that this problem is a result of complex frames being

drawn for the Prefs dialog, and some sort of memory glitch intervening.

However, the problem still exists when you just open one .xul file rather than

the entire frameset.



Simple way to repro:

o  Use advanced-prefs.xul and .dtd to experiment.

o  In the .dtd file, replace a 7-bit ASCII strings with an extended character.

o  Open advanced prefs.

o  Watch Seamonkey die.



Or, open advanced-prefs.xul in Seamonkey

o  In the .dtd file, replace a 7-bit ASCII strings with an extended character.

o  Reload advanced-prefs.xul

o  Nothing is displayed.  (Window goes blank)



This suggests to me that the problems are individual to each XUL file or the

way it's rendered.  Perhaps the <DIV> tag and unicode don't agree?



Adding ftang and tague to the cclist.
Assignee: matt → fergus
I think I have a fix for this.  Re-assigning to me, pending check.
Note:  This applies to UTF-8 characters.  Not surprisingly it also applies to
regular latin-1 extended characters, but that's not a concern.
Blocks: 12394
Status: NEW → ASSIGNED
Target Milestone: M10
Working on a fix for this.
Status: ASSIGNED → RESOLVED
Closed: 20 years ago
Resolution: --- → INVALID
Closing this.  Looks like a red herring.
Status: RESOLVED → VERIFIED
Verified invalid.
You need to log in before you can comment on or make changes to this bug.