- From: <bugzilla@jessica.w3.org>
- Date: Wed, 12 Oct 2011 23:01:48 +0000
- To: public-html-bugzilla@w3.org
http://www.w3.org/Bugs/Public/show_bug.cgi?id=13915 --- Comment #5 from L. David Baron <dbaron@dbaron.org> 2011-10-12 23:01:48 UTC --- That would certainly be an improvement. It even appears to be correct for border="0", based on http://software.hixie.ch/utilities/js/live-dom-viewer/?%3C!DOCTYPE%20html%3E%0A%3Ctable%20border%3D%220%22%3E%3Ctr%3E%3Ctd%3Eno%20style%3C%2Ftable%3E%0A%3Ctable%20border%3D%220%22%20style%3D%22border-width%3A%203px%22%3E%3Ctr%3E%3Ctd%3Eborder-width%3A3px%3C%2Ftable%3E%0A%3Ctable%20border%3D%220%22%20style%3D%22border-style%3A%20solid%22%3E%3Ctr%3E%3Ctd%3Eborder-style%3Asolid%3C%2Ftable%3E%0A%3Ctable%20border%3D%220%22%20style%3D%22border-style%3A%20solid%3B%20border-width%3A%203px%22%3E%3Ctr%3E%3Ctd%3Eborder-style%3Asolid%3C%2Ftable%3E%0A in Gecko and WebKit. It's hard to say off the top of my head whether it's right. This stuff is pretty complicated given the multiple presentational attributes (border, frame, rules) that have effects on tables, cells, and the elements in between -- and it's actually sort of hard to write CSS rules that get the cascading correct so as to get the interactions of those different presentational attributes correct. Gecko actually does implement almost all of this in terms of CSS (rather than C++ code like we used to) -- though the mapping of the border attribute to border-*-width on the table is in C++ (and you describe it in prose), and I needed to sneak in a :-moz-table-border-nonzero selector to handle things like border="0bar". So http://mxr.mozilla.org/mozilla-central/source/layout/style/html.css#257 may be informative here. -- Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the QA contact for the bug.
Received on Wednesday, 12 October 2011 23:01:50 UTC