<TR> is not a block element it is a table-row element </IFRAME> shouldn't be in there that said I see this too if you really want to change the <TR> element to a block element LInux 2003061211
Invalid because TR is not a block element. In CSS it is a table-row element. Reference the duped bug. *** This bug has been marked as a duplicate of 198886 ***
The CSS2 spec has very clear rules for how to handle elements within tables that have the "wrong" display type. This bug is only invalid if our behavior is correct according to those rules. Is it? (That said, using the correct display type (or "") is an easy workaround for the author.)
I'm going by the observation in bug 198886 comment 1. If that's not accurate, then one of these bugs needs to be reopened.
Dbaron: Besides, you also seemed to indicate that this behavior is correct (and the bug invalid) in the past when displaying an element as a non-default non table-* type. Referencing bug 122316. Also referencing BZbarsky's comments in invalid bug 149993. I presume that this behavior is expected to be as such when toggling any table element to block instead of to a table-* type.
CSS2 clearly defines what should happen for various combinations of display types on table-related elements. What CSS2 describes may confuse authors whose expected behavior is "what IE does". That does not mean that our behavior is correct for every case of toggling display types on table elements.
Then we've been resolving a lot of bugs invalid without making that call on what Mozilla should be doing. ::shrug:: I leave it to someone else to decide what, if any, bugs to reopen.
Which bugs other than this one and bug 198886 (which I already reopened and marked duplicate) do you think have been marked invalid without proper analysis? (Just because the bug doesn't have a full explanation of why our behavior is correct doesn't mean that analysis wasn't done in somebody's head.)
Based on what you've said, any bug (such as the ones I've cited -- I know I've seen more like those but I'm not turning Bugzilla upside down today to try and find them) where: * a table element was toggled to a non table-* display value * the result broke the layout (or didn't emulate IE) * the bug was resolved invalid (or dup of a previous invalid) on the basis of http://www.w3.org/TR/REC-CSS2/tables.html#anonymous-boxes or similar logic
In the ones you cited I think people were properly making the call on what Mozilla should be doing.