Bug 20032

Summary: CSS 'content' attribute does not support 'none' or 'normal' values
Product: WebKit Reporter: Quintin May <qmay>
Component: CSSAssignee: Nobody <webkit-unassigned>
Status: RESOLVED CONFIGURATION CHANGED    
Severity: Normal CC: bfulgham, emacemac7, mitz, nicholas, nickshanks, webkit
Priority: P2    
Version: 528+ (Nightly build)   
Hardware: All   
OS: All   
URL: http://www.w3.org/TR/CSS21/generate.html#propdef-content
Attachments:
Description Flags
Example of error
none
Another test case none

Quintin May
Reported 2008-07-14 05:55:03 PDT
The 'none' and 'normal' values for the 'content' attribute are ignored. Setting the value of 'content' to the empty string works.
Attachments
Example of error (387 bytes, application/xhtml+xml)
2008-07-14 05:57 PDT, Quintin May 		no flags
Details
Another test case (679 bytes, text/html)
2009-08-20 01:21 PDT, Yuta Kitamura 		no flags
Details
View All Add attachment proposed patch, testcase, etc.
Quintin May
Comment 1 2008-07-14 05:57:19 PDT
Created attachment 22266 [details] Example of error
Robert Blaut
Comment 2 2008-07-18 15:19:51 PDT
Confirmed issue.
mitz
Comment 3 2008-07-19 13:23:24 PDT
See also bug 13097.
Yuta Kitamura
Comment 4 2009-08-20 01:21:03 PDT
Created attachment 35193 [details] Another test case
Nicholas Wilson
Comment 5 2010-04-12 12:13:31 PDT
Setting content to empty string does *not* work, and should not. 'content: ""' means to render the element, but with no text inside, so, for example, if there is a padding and a background on the pseudo-element it must be drawn. 'content: none' prevents the p-element from being drawn at all. Discuss fix at bug 13097
Brent Fulgham
Comment 6 2022-07-11 16:25:50 PDT
Safari, Chrome, and Firefox show the same rendering behavior for this test case. I do not believe any further compatibility issue remains.
Note You need to log in before you can comment on or make changes to this bug.