13191 2007-03-25 19:09:15 -0700 Webkit doesn’t support content:inherit 2007-03-27 02:24:50 -0700 1 1 1 Unclassified WebKit Layout and Rendering 523.x (Safari 3) Mac OS X 10.4 RESOLVED DUPLICATE 13097 P2 Normal --- 1 david webkit-unassigned mitz oldest_to_newest 17328 0 david 2007-03-25 19:09:15 -0700 On CSS specifities: * Here in English, but I don’t find it that clear: http://meyerweb.com/eric/css/link-specificity.html * Here in French (I’ll try to translate it one day): http://blog.empyree.org/post/2837 The test case uses two styles (in that writing order): /* specificity 0,0,2 */ html table :before, html table :after {content:inherit} /* specificity 0,0,1 */ abbr:after {content:" ("attr(title)")"} Even though it is the last one, the second one shall be overridden by the first, by virtue of specificities. This is the case with Opera (I did not check with Gecko). 17329 1 13817 david 2007-03-25 19:10:08 -0700 Created attachment 13817 Testcase 17330 2 hyatt 2007-03-25 20:39:00 -0700 WebKit just ignores content:inherit right now, since it's kind of a crazy thing to right in CSS2.1 when it can only apply to generated content. 17313 3 mitz 2007-03-25 22:52:44 -0700 Now looks like a duplicate of bug 13097. 17312 4 hyatt 2007-03-25 23:10:38 -0700 *** This bug has been marked as a duplicate of 13097 *** 17192 5 david 2007-03-27 01:42:44 -0700 Shall I understand this is the same mechanism that governs inheritance and specificity? Even if this is the case, it appeared to me as two different applications of the same problem, and it would be worth checking the two of them, but you certainly know better (no irony in this sentence—you’re just better than me at developping a browser). 17175 6 hyatt 2007-03-27 01:48:21 -0700 We ignore content:inherit completely. This is why it looked like a specificity issue (when it wasn't). 17176 7 david 2007-03-27 02:24:50 -0700 (In reply to comment #6) > We ignore content:inherit completely. This is why it looked like a specificity > issue (when it wasn't). > Thank you. Do you have an approximation on when you will start working on content:inherit? At least for compatibility reasons with Opera (and maybe even for standards reason, but I am not sure here), content="" will have hideous side effects on Opera, contrary to content inherit Example: table :before, table :after {content:inherit /* For space reaason, I avoid any generated content in a table. Do not use content:"", or it will break in Opera — plus, this is not the intended effect*/} 13817 2007-03-25 19:10:08 -0700 2007-03-25 19:10:08 -0700 Testcase specificites.xhtml application/xhtml+xml 801 david PD94bWwgdmVyc2lvbj0iMS4wIiBlbmNvZGluZz0idXRmLTgiPz4KPD94bWwtc3R5bGVzaGVldCBo cmVmPSJzY3JlZW4uY3NzIiB0eXBlPSJ0ZXh0L2NzcyIgbWVkaWE9InNjcmVlbiI/Pgo8IURPQ1RZ UEUgaHRtbCBQVUJMSUMgIi0vL1czQy8vRFREIFhIVE1MIDEuMS8vRU4iICJodHRwOi8vd3d3Lncz Lm9yZy9UUi94aHRtbDExL0RURC94aHRtbDExLmR0ZCI+CjxodG1sIHhtbG5zPSJodHRwOi8vd3d3 LnczLm9yZy8xOTk5L3hodG1sIiB4bWw6bGFuZz0iZW4iPgo8aGVhZD4KCTx0aXRsZT5LbmlnaHQg b2YgdGhlIFdoaXRlIE1vdW50YWluPC90aXRsZT4KCTxzdHlsZSB0eXBlPSJ0ZXh0L2NzcyI+Cglo dG1sIHRhYmxlIDpiZWZvcmUsIGh0bWwgdGFibGUgOmFmdGVyIHtjb250ZW50OmluaGVyaXQgLyog c3BlY2lmaWNpdHkgMCwwLDIgKi99CglhYmJyOmFmdGVyICAgICAgICAgIHtjb250ZW50OiIgKCJh dHRyKHRpdGxlKSIpIiAvKiBzcGVjaWZpY2l0eSAwLDAsMSAqL30KCTwvc3R5bGU+CjwvaGVhZD4K Cjxib2R5Pgo8dGFibGU+CjxjYXB0aW9uPkEgdGFibGU8L2NhcHRpb24+Cjx0aGVhZD4KPHRyPgoJ PHRoPkhlYWRlciAxPC90aD4KCTx0aD48YWJiciB0aXRsZT0iWU9VIEFSRSBOT1QgU1VQUE9TRUQg VE8gU0VFIFRISVMiPkhlYWRlciAyPC9hYmJyPjwvdGg+Cgk8dGg+SGVhZGVyIDM8L3RoPgo8L3Ry Pgo8L3RoZWFkPgo8dGJvZHk+Cjx0cj4KCTx0ZD52YWx1ZSAxPC90ZD4KCTx0ZD52YWx1ZSAyPC90 ZD4KCTx0ZD52YWx1ZSAzPC90ZD4KPC90cj4KPC90Ym9keT4KPC90YWJsZT4KPC9ib2R5Pgo8L2h0 bWw+