Using Mozilla/5.0 (Windows; U; WinNT4.0; en-US; m18) Gecko/20001116 and Netscape 6 If fields in a form are hidden with display:none, their values cannot be accessed through JavaScript. It also appears that switching the display attribute does not undo this problem. (See test case) This is probably related to the form submission problem described in bug 34297

Formcontrol/presState problem, over to rods.

as far as I can tell, this is an editor bug and I think it is a dup - reassigning

I don't follow what you mean when you say this is an editor bug. This code was created by hand. The code behaves as expected in IE 5 (JavaScript can access display:none form fields' values). Still occurs in Mozilla 2000112704. This bug should probably have the correctness and dataloss keywords, so I'm adding them.

Duplicate of bug 34297 'form controls with style="display: none;" unsuccessful in Mozilla' And Have to do with bug 52334 Problems with contentDocument and 'display:none' in IFRAMES.

No, this is not a duplicate of bug 34297. Bug 34297 is a problem with form submission and fields with display:none. This bug is a problem with the DOM (JavaScript access to fields with display:none). They may be related problems but they are different.

handing this over to the dom folks to see if they can help resolve this

Sounds like a pres state problem, rods usually deals with those so I'm handing this over to him.

VERIFIED Platform: PC OS: Linux 2.2.16 Mozilla Build: 2000122808 Trunk Build Marking NEW.

I think this is a dup

Taking QA Contact on all open or unverified DOM Style bugs...

Setting milestone to future. This will be addressed when the XBL implementation of the form elements lands.

This should be fixed with the complete fix to bug 34297. Initial values are not being set when display: none. Note that with textboxes setting display: block and then display: none again seems to work (see bug 34297). At any rate, when we're done with that patch we shouldn't be talking to frames for their values anymore. I suggest a bug dependency.

*** Bug 100533 has been marked as a duplicate of this bug. ***

Fixed with bug 34297 landing.