Closed Bug 12406 Opened 25 years ago Closed 25 years ago

Native form elements and divs

Categories

(Core :: Layout: Form Controls, defect, P3)

Product:
Core
Component:
Layout: Form Controls
Platform:
x86
Windows NT
Type:
defect

Tracking

()

Status:
VERIFIED FIXED

People

(Reporter: rjainend, Assigned: kmcclusk)

Details

(Whiteboard: waiting for engineer feedback) 

question about native form elements and layers (divs).  will the native
elements still have the highest z index so that divs will always lie under
them?  this is the behavior seen in the current navigator versions.  it would
be great if native elements (<!-- <FORM><INPUT TYPE=text></FORM> -->) could be
placed underneath divs (layers).

i would appreciate a response since a lot of oracle crm applications are using
dhtml.
Assignee: don → karnaze
Component: Browser-General → HTML Form Controls
Assignee: karnaze → kmcclusk
This was opened on 8/24 so it is a mystery why I'm just now getting it.
Reassigning to Kevin.
Status: NEW → RESOLVED
Closed: 25 years ago
Resolution: --- → FIXED
It is planned that ALL HTML form elements will obey z-index when intermixed with
other HTML elements.

Currently:
Buttons, checkboxes, and radio buttons honor z-index.
Listboxes honor z-index, but their scrollbars do not.
Text fields and text areas, do not honor z-index yet.
Updating QA Contact.
QA Contact update.
kmcclusk, by marking this resolved fixed, is it safe to assume that listbox
scrollbars, text fields, and textareas all honor z-index?
Whiteboard: waiting for engineer feedback
I think I marked it fixed because I answered the question and I all of the 
remaining issues to support z-index are covered by other bugs. We could open a 
new bug for the remaining issues and add dependencies, but the bug would be 
completely solved when gfx-scrollbars are used everywhere and text fields no 
longer use native-widgets.
Agreed.  Thanks Kevin!
Marking VERIFIED FIXED on:
- Linux6 2000-03-07-09 Commercial build
- MacOS9 2000-03-07-08 Commercial build
- Win98 2000-03-07-09 Commercial build
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.