> > I wonder if other elements redefined as tables by CSS properties are also
> > affected?
>
> Yeah, they should be. In fact, a <table> element is essentially just
> implemented as a generic element "redefined as tables by CSS properties" -- see
> http://mxr.mozilla.org/mozilla-central/source/layout/style/html.css#180
We may be back to the border-collapse trail mentioned in comment #9, then. I only found this bug because I've just been hit by it, and my "border: 2px solid black" tables were suddenly borderless. But only the tables; I've got plenty of other "border: 2px solid #xxx" elements with correct rendering (mostly div and p). The only difference I can see between those elements is the border-collapse. Just now, using Firebug to disable only this property, the borders came back.
(In reply to comment #21)
> > I wonder if other elements redefined as tables by CSS properties are also mxr.mozilla. org/mozilla- central/ source/ layout/ style/html. css#180
> > affected?
>
> Yeah, they should be. In fact, a <table> element is essentially just
> implemented as a generic element "redefined as tables by CSS properties" -- see
> http://
We may be back to the border-collapse trail mentioned in comment #9, then. I only found this bug because I've just been hit by it, and my "border: 2px solid black" tables were suddenly borderless. But only the tables; I've got plenty of other "border: 2px solid #xxx" elements with correct rendering (mostly div and p). The only difference I can see between those elements is the border-collapse. Just now, using Firebug to disable only this property, the borders came back.