35598 - HTMLInputElement.click does not function

Status: RESOLVED FIXED

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

Description

[ckritzer (gone)]

Overview:  When using HTMLInputElement.click() to simulate a mouse click on a 
checkbox or radio button, nothing appears to happen.  Checkboxes, radiobuttons 
do not change states.

Steps to Reproduce:
1) Launch Commercial builds of 0411xx on Linux, MacOS, and/or Win32
2) Load attached testcase

Actual Results: Checkbox and radio buttons do not change checked states

Expected Results:  Checkbox and radio buttons should change checked states

Platforms Tested/Bug Exists On:
- Linux6 2000-04-11-09 Commercial
- MacOS9 2000-04-11-09 Commercial
- Win98  2000-04-11-09 Commercial

Comment 1

[ckritzer (gone)]

Attachment: Testcase for HTMLInputElement.click()

Comment 2

[ckritzer (gone)]

QA Contact set to self.  Updated OS to 'All'.

Comment 3

[ckritzer (gone)]

nominating for nsbeta2: severity, feature (DOM Level 1 Standards Compliance) 
broken

Comment 4

[leger]

Putting on [nsbeta2-] radar.   Unless you can give us a top 100 site with this 
problem.

Comment 5

[leger]

Per gerardo's mail, info below" removing nsbeta- for a re-eval by PDT

"Yes, the HTMLInput.click() method would need to work on the feature complete 
build (beta2) if we want to claim that DOM is supported in NS 6. The Beta2 
criteria states that: 

     "DOM Level 0 (the DOM elements founds in Nav3/JavaScript 1.1) must be
     fully supported. Bugs in support for DOM0 should be carefully evaluated as
     possible beta 2 stoppers as they will affect many pages."

The HTMLInput.click() was implemented in Navigator 2.0 --see Netscape Reference.
Currently, the click() method is not working at all, no matter what data is 
used, in the simplest possible test scenario. I'm not ready to give you a top 
100 site yet."

Comment 6

[leger]

Putting on [nsbeta2+] radar.

Comment 7

[Johnny Stenback (:jst)]

The attached testcase is a bit broken, I'll attach an fixed version.

Comment 8

[Johnny Stenback (:jst)]

Attachment: Fixed testcase

Comment 9

[troy]

Johnny, the test case you attached works fine on today's win32 build.  Please 
check this out on Linux and, if it works there too, please mark this bug fixed.  
Thanks!

Comment 10

[Johnny Stenback (:jst)]

Thanks for testing Troy, I tested on Linux and looks good there too.

Marking FIXED.

Comment 11

[ckritzer (gone)]

Marking VERIFED FIXED on:
 - MacOS9 2000-05-23-12-M16 Commercial Build
 - Linux6 2000-05-23-10-M16 Commercial Build
 - Win95 2000-05-23-10-M16 Commercial Build

Comment 12

[ckritzer (gone)]

Marking VERIFED FIXED on:
 - MacOS9 2000-05-23-12-M16 Commercial Build
 - Linux6 2000-05-23-10-M16 Commercial Build
 - Win95 2000-05-23-10-M16 Commercial Build

Comment 13

[Bernd]

I opened attachment 8335 [details] the second checkbox is not selected and the second
radiobutton is selected where the testcase claims it should be the third.
reopening the bug

Comment 14

[Fabian Guisset]

Confirmed in 0.9.6. Wow how did that happen. The click() on the button works though.

Comment 15

[David W. Jeske]

Another case of this bug is INPUT TYPE=IMAGE, here is a test case:

http://mozart.chat.net/~jeske/_drop/Mozilla/sample1.html

Comment 16

[Johnny Stenback (:jst)]

Mass-reassigning bugs to [e-mail]

Comment 17

[Phil DeJarnett]

I think this is also a problem with <input type="file">.  I want to customize
the look of a file upload box.  Under IE, I can use a JavaScript function to do
"document.form.filebox.click()", and it will open the Browse window.

Under Mozilla, nothing whatsoever happens.  On a related note, apparently the
onChange isn't called when the information is updated via the browse button.

If this isn't a related bug, please let me know so I can file a new one!

Comment 18

[Christopher Aillon (sabbatical, not receiving bugmail)]

Phil, this was a generic bug.  If there is a specific bug for a specific type of
inputs, I'd say file that separately (although I suspect what you mentioned is
not really a bug with .click() -- I imagine the click event is getting fired,
but it is on the textbox portion, and not the button portion which is anonymous
content...)

Marking FIXED.