Bug 20032 - CSS 'content' attribute does not support 'none' or 'normal' values
Summary: CSS 'content' attribute does not support 'none' or 'normal' values
Status: RESOLVED CONFIGURATION CHANGED
Alias: None
Product: WebKit
Classification: Unclassified
Component: CSS (show other bugs)
Version: 528+ (Nightly build)
Hardware: All All
: P2 Normal
Assignee: Nobody
URL: http://www.w3.org/TR/CSS21/generate.h...
Keywords:
Depends on:
Blocks:
 
Reported: 2008-07-14 05:55 PDT by Quintin May
Modified: 2022-07-11 16:25 PDT (History)
6 users (show)

See Also:


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

Note You need to log in before you can comment on or make changes to this bug.
Description Quintin May 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.
Comment 1 Quintin May 2008-07-14 05:57:19 PDT
Created attachment 22266 [details]
Example of error
Comment 2 Robert Blaut 2008-07-18 15:19:51 PDT
Confirmed issue. 
Comment 3 mitz 2008-07-19 13:23:24 PDT
See also bug 13097.
Comment 4 Yuta Kitamura 2009-08-20 01:21:03 PDT
Created attachment 35193 [details]
Another test case
Comment 5 Nicholas Wilson 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
Comment 6 Brent Fulgham 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.