236324 - malfunction of javascript confirm function in firefox

Status: RESOLVED WORKSFORME

(Firefox :: General, defect)

Description

[Adrian Spinei]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.6) Gecko/20040206 Firefox/0.8
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.6) Gecko/20040206 Firefox/0.8

Hooking a confirm function in onclick event of a link tag does not perform as
expected. The link is launched no matter what the confirmation status is, as a
matter of fact the link is launched BEFORE clicking on any button in the confirm
box. However, returning hardcoded false in the onclick event stops the link.
Not functioning:
<A HREF="http://www.google.com" onclick="javascript:return confirm('yep
?');">google</A>
Functioning:
<A HREF="http://www.google.com" onclick="javascript:return (false);">google</A>

Reproducible: Always
Steps to Reproduce:
1.Create a test page with a link and confirm on onclick event
2.Try

Actual Results:  
link launched before opting in the confirm box

Expected Results:  
browser should wait for confirmation and launch the link ONLY if ok

Works in IE. This is classic Javascript stuff.

Comment 1

[Adrian Spinei]

Attachment: simple web page displaying the bug

Comment 2

[José Jeria]

WFM: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.7b) Gecko/20040302
Firefox/0.8.0+

Comment 3

[Adrian Spinei]

It does work after restarting Firefox ! Will try to reproduce and come back for
more details.

Comment 4

[Kelemen Zoltan]

Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.6) Gecko/20040320 Firefox/0.8

I can confirm the same behaviour on Linux as well (It's actually a Gentoo
Firefox 0.8-r1 build)

And restarting does not help, to me it seems as always reproducible.

Comment 5

[José Jeria]

Can anyone with a nighlty build reproduce this? So far this seems to only
happend in 0.8

Comment 6

[Kelemen Zoltan]

With the latest nightly build available at this time (Mozilla/5.0 (X11; U; Linux
i686; en-US; rv:1.7b) Gecko/20040326 Firefox/0.8.0+), the bug is not
reproducible, the browser behaves as expected.

Comment 7

[Jason Barnabe (np)]

Since it works for everyone, I'm marking this as WORKSFORME. Reopen if it still
occurs on a recent nightly build.