CSS support in browsers
Revised: It looks like I originally mischaracterized the bug. The real bug seems to be that Netscape will not allow CSS padding or margin settings to be set for a TD element. IE, on the other hand, won’t let them be set for a SPAN element. Both render the code correctly if they are set for a DIV element. Go figure.
Well, I just did something very stupid that resulted in me losing the entirety of the new post I just typed. So, I’ll type it again and try to be less stupid this time. The post went as follows:
Anyone care to know of a Netscape CSS bug? If a class is defined, given the name “body”, and selected into an element, e.g., <SPAN class=”body”>some spanned text</SPAN>, Netscape takes a serious nose dive. This is true for Netscape 4 in Windows as well as whatever Mac version my friend Petra (who reported the problem to me) uses. In Windows the crash is particularly ugly, causing an invalid page fault and bringing up one of those terminal dialog boxes that can never be dismissed (nor can the OS be restarted, so it’s a hard reboot.) This problem may extend to other element names, but I don’t want to use any of my machines as a test subject.
I can’t see anything in the CSS spec that forbids name overlap between classes and elements. But even if there were, surely there should be a more graceful failure route. I might report this at some point, but it is hard to gather the motivation as (1) I don’t use Netscape and (2) I very rarely get responses when I submit bug reports.
And I think that is pretty much verbatim what I had there before.
Email subscription
April 24th, 2007 at 2:54 pm
[...] mcgees.org « CSS support in browsers Nutritional toxicology » [...]