Closed
Bug 233316
Opened 22 years ago
Closed 21 years ago
crash when selecting radiobutton and/or tabbing thru form fields
Categories
(Core :: Layout: Form Controls, defect)
Tracking
()
RESOLVED
WORKSFORME
People
(Reporter: hennessy, Unassigned)
References
()
Details
(Keywords: crash, stackwanted)
User-Agent:
Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7a) Gecko/20040202
When I tab thru or select radiobutton formfields, Mozilla crashes.
Reproducible: Always
Steps to Reproduce:
1.enter form values, tabbing between them
2.tab to or pick a radio button
3.*poof*
Actual Results:
crashed
Expected Results:
not crashed
(selected radio button)
Comment 1•22 years ago
|
||
Worksforme on this page, with linux trunk build pulled at "Wed Feb 4 03:53:37
CST 2004"
Could you attach a testcase showing the problem?
Comment 2•22 years ago
|
||
sounds like bug 232368, except that the page here has no blur/focus handlers.
are you getting a crash (Mozilla exits) or hang (freeze)?
worksforme with linux trunk 20040206
==> form controls
Assignee: form-submission → nobody
Component: HTML: Form Submission → Layout: Form Controls
Keywords: crash
QA Contact: core.layout.form-controls
Hi,
I'm getting a crash, which brings down all windows and exits.
Building from CVS broke for me on Fri, I'll try rebuilding with debug enabled on
monday (I had been building --enable-final and debug disabled 'cuz I use it as
my primary day-to-day browser) to try and get anything useful.
Comment 4•22 years ago
|
||
do you still crash using Mozilla 1.7rc2 ? If so, please post Talkback Incident
ID for this crash by running "mozilla/components/talkback/talkback"
Severity: normal → critical
Keywords: stackwanted
Comment 5•21 years ago
|
||
WFM, 2005-01-28-05 trunk Linux
WFM, 2005-01-28-04 trunk Windows XP
A lot of stuff have been fixed since 1.7a - please try a recent version
and file a new bug report if the problem still occurs, thank you.
-> WORKSFORME
Status: UNCONFIRMED → RESOLVED
Closed: 21 years ago
Resolution: --- → WORKSFORME
You need to log in
before you can comment on or make changes to this bug.
Description
•