Bug 13191 - Webkit doesn’t support content:inherit
Summary: Webkit doesn’t support content:inherit
Status: RESOLVED DUPLICATE of bug 13097
Alias: None
Product: WebKit
Classification: Unclassified
Component: Layout and Rendering (show other bugs)
Version: 523.x (Safari 3)
Hardware: Mac OS X 10.4
: P2 Normal
Assignee: Nobody
Depends on:
Reported: 2007-03-25 19:09 PDT by David Latapie
Modified: 2007-03-27 02:24 PDT (History)
1 user (show)

See Also:

Testcase (801 bytes, application/xhtml+xml)
2007-03-25 19:10 PDT, David Latapie
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description David Latapie 2007-03-25 19:09:15 PDT
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).
Comment 1 David Latapie 2007-03-25 19:10:08 PDT
Created attachment 13817 [details]
Comment 2 Dave Hyatt 2007-03-25 20:39:00 PDT
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.

Comment 3 mitz 2007-03-25 22:52:44 PDT
Now looks like a duplicate of bug 13097.
Comment 4 Dave Hyatt 2007-03-25 23:10:38 PDT

*** This bug has been marked as a duplicate of 13097 ***
Comment 5 David Latapie 2007-03-27 01:42:44 PDT
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).
Comment 6 Dave Hyatt 2007-03-27 01:48:21 PDT
We ignore content:inherit completely.  This is why it looked like a specificity issue (when it wasn't).
Comment 7 David Latapie 2007-03-27 02:24:50 PDT
(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

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*/}