[Webkit-unassigned] [Bug 65968] New: Setting the content css property on img elements has unpredictable and unexpected results
bugzilla-daemon at webkit.org
bugzilla-daemon at webkit.org
Wed Aug 10 01:59:03 PDT 2011
https://bugs.webkit.org/show_bug.cgi?id=65968
Summary: Setting the content css property on img elements has
unpredictable and unexpected results
Product: WebKit
Version: 528+ (Nightly build)
Platform: Unspecified
URL: http://jsfiddle.net/AAw9w/
OS/Version: Unspecified
Status: UNCONFIRMED
Severity: Normal
Priority: P2
Component: Layout and Rendering
AssignedTo: webkit-unassigned at lists.webkit.org
ReportedBy: jaffathecake at gmail.com
The CSS3 spec allows the 'content' property on all elements (not just pseudo elements such as ::before), as far as I know this isn't supported in Webkit currently, but it appears to have some effect on img elements.
http://jsfiddle.net/AAw9w/
http://jsfiddle.net/AAw9w/show/
View those pages & hit refresh a few times. Sometimes an img is displayed, sometimes nothing. The img sometimes displayed is the one specified by the 'content' property in the css.
Setting 'content' to a string, which should be displayed instead of the image, results in no output.
Expected behaviour would be to display the img as specified in the content property of the css (ideally not downloading the original img), or ignore the rule if it's unsupported.
Tested in: Safari 5.1, Chrome 13, Chrome Canary all on OSX 10.6.8.
--
Configure bugmail: https://bugs.webkit.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
More information about the webkit-unassigned
mailing list