Summary: | Webkit doesn’t support content:inherit | ||||||
---|---|---|---|---|---|---|---|
Product: | WebKit | Reporter: | David Latapie <david> | ||||
Component: | Layout and Rendering | Assignee: | Nobody <webkit-unassigned> | ||||
Status: | RESOLVED DUPLICATE | ||||||
Severity: | Normal | CC: | mitz | ||||
Priority: | P2 | ||||||
Version: | 523.x (Safari 3) | ||||||
Hardware: | Mac | ||||||
OS: | OS X 10.4 | ||||||
Attachments: |
|
Description
David Latapie
2007-03-25 19:09:15 PDT
Created attachment 13817 [details]
Testcase
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. *** This bug has been marked as a duplicate of 13097 *** 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). We ignore content:inherit completely. This is why it looked like a specificity issue (when it wasn't). (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*/} |