CSS & Form Fields

[kwilliams]

I have pure CSS menus for our site, and they work great. But they don't load in front of the form fields on the page. My old JavaScript menu did the same thing. I remember asking about this a few years ago, and I also remember someone saying that it's because since the CSS and JavaScript load before the HTML on a web page, they have priority in the scheme of things. Am I correct, or is there another reason for this? Also, is there a fix for this somewhere, or is it not possible to fix? Thanks for any clarification.

[Little Goat]

I'm not sure what you mean... link? code?
LG

[ray326]

I don't think you can count on being able to control that because the form widgets are rendered by the browser, generally using services from the OS they're running on.

[kwilliams]

Little Goat: I'm not sure what you mean... link? code?
Sorry about that. Here's a link to an example page that loads the menus behind the form's select menus: http://www.douglas-county.com/local_govt/minutes.asp.

ray326: I don't think you can count on being able to control that because the form widgets are rendered by the browser, generally using services from the OS they're running on.
I understand what you're saying, as when I then tried in in Firefox, they loaded in front of the form's select menus. But in IE (of course), they load behind the form's select menus.

So since other things are created and/or hacked in CSS to make them act the same in IE as they do for every other proper browser, is there something that I can add to the CSS would make the CSS menus load in front of the select menus in all browsers, including IE? Thanks again for any help.

[ray326]

So since other things are created and/or hacked in CSS to make them act the same in IE as they do for every other proper browser, is there something that I can add to the CSS would make the CSS menus load in front of the select menus in all browsers, including IE? Thanks again for any help.No, because the widgets aren't rendered entirely by code in the browser.

[kwilliams]

No, because the widgets aren't rendered entirely by code in the browser.

Ok, so that means I have no control over how the pure CSS popups load in IE when it comes to form fields. Correct?

[Little Goat]

try putting the code for the menus after the code for the form. then use css positioning to put it before.
LG

[kwilliams]

Maybe I'll give that a try another time. I think that's a lot of hassle to get something to work properly in one browser, when all others do in fact render it in the correct way.

I'm using CSS positioning for my new site, and although I love the freedom of not using tables for layouts, it was a very time-consuming process to initially set it up. So I think that I'll just wait to fix the problem by uploading my new site in a few months. But thanks for your input...it's greatly appreciated.

[ray326]

Think about it. Which one out of ALL the browsers out there is most likely to to do direct OS calls to handle bits of its rendering. Cross-platform browsers have to do everything but the IE programmers know they can call Windows to create widgets at specific places on the screen which happen to be on top of the client area of IE. Of course they are on top of everything else in the client area that's being drawn by the browser.

[kwilliams]

Think about it. Which one out of ALL the browsers out there is most likely to to do direct OS calls to handle bits of its rendering. Cross-platform browsers have to do everything but the IE programmers know they can call Windows to create widgets at specific places on the screen which happen to be on top of the client area of IE. Of course they are on top of everything else in the client area that's being drawn by the browser.

So there's really nothing that I can do on my side to correct his problem, because each browser's going to render the code how it wants to...correct?

[ray326]

Correct. What some people do as a work around is hide the page content when the menu drops.