Last Comment Bug 670528 - FF5+: [link].click no longer returns undefined, though [link].click() still unsupported.
: FF5+: [link].click no longer returns undefined, though [link].click() still u...
Product: Core
Classification: Components
Component: DOM: Core & HTML (show other bugs)
: 5 Branch
: All All
-- normal (vote)
: ---
Assigned To: Nobody; OK to take it and work on it
: Andrew Overholt [:overholt]
Depends on: 666604
  Show dependency treegraph
Reported: 2011-07-10 08:04 PDT by pete.j.scott
Modified: 2011-07-13 20:37 PDT (History)
2 users (show)
See Also:
Crash Signature:
QA Whiteboard:
Iteration: ---
Points: ---
Has Regression Range: ---
Has STR: ---

index.html (534 bytes, text/html)
2011-07-10 08:04 PDT, pete.j.scott
no flags Details

Description User image pete.j.scott 2011-07-10 08:04:27 PDT
Created attachment 545074 [details]

User Agent: Mozilla/5.0 (X11; Linux i686; rv:6.0) Gecko/20100101 Firefox/6.0
Build ID: 20110705195857

Steps to reproduce:

Tested code to avoid firing click() on an anchor element by checking for (, 
if ( {; }

[ATTACHED AS index.html].

Actual results: returns a function in Firefox 5.0 and Firefox 6.0. Previously (FF3.6, FF4.0) it returned 'undefined'. This causes existing code that allows calls when != 'undefined' to fire, which does not work (and does not throw error, simply fails to execute).

Expected results:

I would expect to continue returning 'undefined', since is still not supported by Firefox.
Comment 1 User image j.j. 2011-07-10 10:27:27 PDT
This should be fixed with bug 666604 in Firefox 7.

Please download and test with Firefox 7 Aurora build, thanks!
Comment 2 User image pete.j.scott 2011-07-13 11:47:18 PDT
Confirmed fixed with Firefox 7 Aurora build 7.0a2. Thanks!
Comment 3 User image j.j. 2011-07-13 14:47:06 PDT
-> FIXED with bug 666604
Comment 4 User image Boris Zbarsky [:bz] (still a bit busy) 2011-07-13 20:36:55 PDT
Note that does in fact execute and does what it's supposed to: fires an untrusted click event on the anchor.  If you have an onclick listener, it will get triggered....

Note You need to log in before you can comment on or make changes to this bug.