thanks.
think i've got it fixed now.
i had the search box inputs inside a <fieldset> tag that was set to 'display: inline' with css. apparently, IEmac doesn't like that much and decided that instead of meaning 'turn a block element into an inline element' it means "don't display this element at all and instead, make the div containing it take up the background of the entire page."
i used to hate NN4. but it really causes very few problems for me these days. i do all my layout with css and @import the stylesheet so NN4 doesn't see it and gets a plain old, unformated version instead. now it's IE/mac that's giving me the most grief. it seems to have the most bugs and the strangest interpretations of the CSS standards.
coding css to the standards, i can write the stylesheet and expect it to work in mozilla, opera, and IE/win. the few areas where those browsers don't agree, they at least tend to degrade gracefully.
at least i know a trick for hiding css from IE/mac similar to how @import hides css from NN4. so if i ever get too tired of supporting the broken css implementation, i can just give up and give it the same plain, default layout.
anders pearson - 2002-05-04 17:57:46
thanks. think i've got it fixed now. i had the search box inputs inside a <fieldset> tag that was set to 'display: inline' with css. apparently, IEmac doesn't like that much and decided that instead of meaning 'turn a block element into an inline element' it means "don't display this element at all and instead, make the div containing it take up the background of the entire page." i used to hate NN4. but it really causes very few problems for me these days. i do all my layout with css and @import the stylesheet so NN4 doesn't see it and gets a plain old, unformated version instead. now it's IE/mac that's giving me the most grief. it seems to have the most bugs and the strangest interpretations of the CSS standards. coding css to the standards, i can write the stylesheet and expect it to work in mozilla, opera, and IE/win. the few areas where those browsers don't agree, they at least tend to degrade gracefully. at least i know a trick for hiding css from IE/mac similar to how @import hides css from NN4. so if i ever get too tired of supporting the broken css implementation, i can just give up and give it the same plain, default layout.