Closed Bug 61811 Opened 24 years ago Closed 24 years ago

flex="-1" crashes mozilla: Floating point exception

Categories

(Core :: XUL, defect, P4)

x86
Linux
defect

Tracking

()

VERIFIED WORKSFORME
mozilla0.9

People

(Reporter: havardda-mozilla, Assigned: eric)

Details

even though flex="-1" isn't very helpful, moz should manage to keep her self alive. (flex="-1" doesn't break anything if the xul is loaded directly and not in the sidebar.) This is the errormsg as dumped to the console: /home/apollo/havardda/mozilla/run-mozilla.sh: line 72: 24025 Floating point exception$prog ${1+"$@"}
Shouldn't Mozilla just ignore a negative flex value entirely?
[--> XP Toolkit/Widgets: XUL]
Component: Sidebar → XP Toolkit/Widgets: XUL
reassigning.
Assignee: matt → trudelle
QA Contact: shrir → jrgm
->evaughan, p4/moz0.9, since this presumably affects only XUL developers. Where is the flex=-1 being used?
Assignee: trudelle → evaughan
Priority: P3 → P4
Target Milestone: --- → mozilla0.9
I'm trying to recreate the crash, but using a nightly build from yesterday, it seems that flex="-1" isn't a problem any more. FYI, the crash occured only when the xul data was loaded in the sidebar, and the attribute could appear in any element. I'll try some more to recreate the bug (and publish a test case if need be), but I really do think the bug is solved :)
Marking worksforme per reporter's last comment. Please reopen if this rears its ugly head again.
Status: UNCONFIRMED → RESOLVED
Closed: 24 years ago
Resolution: --- → WORKSFORME
Lots of verifications. If I had to test stuff, it was on Win2K, build id 2001052404.
Status: RESOLVED → VERIFIED
Component: XP Toolkit/Widgets: XUL → XUL
QA Contact: jrgmorrison → xptoolkit.widgets
You need to log in before you can comment on or make changes to this bug.