185888 - crash every time a click on ' JavaScript:SWESubmitForm(document.SWEForm8_0,c_12,"","1-ONMXZ") '

Status: RESOLVED INVALID

(Core :: DOM: Core & HTML, defect)

Description

[Geotronix]

User-Agent:       Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.2.1) Gecko/20021210 Debian/1.2.1-3
Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.2.1) Gecko/20021210 Debian/1.2.1-3

My home banking site gives me problems I never had with 1.1 series. It's manly
based on java and when I ask details about my account it simply crashes. This is
the text that underlies those buttons.

JavaScript:SWESubmitForm(document.SWEForm8_0,c_12,"","1-ONMXZ")

Any idea of what's causing this.

Thanks.

Reproducible: Always

Steps to Reproduce:
1.Go on my home banking site 'www.banca-primavera.it (sorry can't give paswords ;-))
2.Login in;
3.ask details about account and view the crash

Actual Results:  
nothing

Expected Results:  
Continued view of the html file.

Comment 1

[Phil Schwartau]

Not likely to be JS Engine; reassigning to Form Submission
until we can get a stack trace. 

[e-mail]: could you download a Talkback-enabled build?
After you crash, fill out the Talkback form and submit it to us.

Then you can look up the Talkback ID for each crash by running 
mozilla/components/talkback. Please post these IDs to this bug,
and then we can look up the stack traces; thanks -

Comment 2

[Brant Gurganus]

By the definitions on <http://bugzilla.mozilla.org/bug_status.html#severity> and
<http://bugzilla.mozilla.org/enter_bug.cgi?format=guided>, crashing and dataloss
bugs are of critical or possibly higher severity.  Only changing open bugs to
minimize unnecessary spam.  Keywords to trigger this would be crash, topcrash,
topcrash+, zt4newcrash, dataloss.

Comment 3

[Mikael Parknert]

Reporter: Can you reproduce this bug with a recent build of Mozilla (for
example, 1.4rc2)? 

If so, then please comment again with details. 
If not, then please resolve this bug as WORKSFORME. Thanks.

Comment 4

[Alistair Y. Lewars]

Reporter, as stated by Makael, please try again with a recent build (with
talkback enabled so that we can get a stacktrace) to see if this bug is still
present.

Thanks.

Comment 5

[Sven Krohlas]

Reporter, are you able to reproduce this with a current build?
If you aren't or you don't say anything at all we'll mark this bug WFM.
So please add a comment :-))

Comment 6

[Felix Miata]

Due to the password problem this can't be tested, and the reporter has never
replied. Marking invalid since over a year old.