Sunday, 5th June 2005
Talk to me
Kevin pointed out half an hour ago that no one using IE could see the input fields on my comments form. I rushed over to check — true, there was a big blank piece of background where my inputs and labels should have been. You could still click on (or tab to) an input, and end up with a blinking text cursor on a blank background, but that was it.
What caused this? Well, ten days ago I took out the MT-default inline CSS, and put it in my stylesheet. And had the audacity to left-float my new div.inputs. So IE vanished it. Of course. (Actually, IE did this with my blogpost titles too, which is why, instead, IE gets them on one line. Grrr.)
So, IE now gets a non-floating, and visible, comments form. Happy?
Comments
I didn't think anyone still used IE but presumably Kevin must have done so.
According to TheCounter.com, IE still has an 80-85% market share globally. Even on this blog, I get about 55-60% IE users (compared with 20% Firefox).
To be honest, since SP2 came out IE hasn't been that bad (as an end-user experience, not in terms of CSS authoring obviously :-) ), especially if you're using a shell like Maxthon (which Kevin was). It certainly blocks popups better than FF, which seems to be slipping again, and I think it's more stable than FF (though I haven't used IE all day for quite a while, so I can't be sure). If you know how to use a computer properly it doesn't pose any greater security threat than other rendering engines either.
Plus it was my own stupid fault for not testing in IE after I'd made a (seemingly innocuous) CSS change... :-)
add a comment