Le 22 oct. 2012 à 08:25, Philip TAYLOR <[email protected]> a écrit :
> According to : > > http://www.w3.org/TR/CSS21/generate.html#content > > the computed value of the "content" attribute for an element > (/qua/ element) is "normal"; Seamonkey and Internet Explorer > both respect this, and render : > > <SPAN style="content: 'bar'">foo</SPAN> > > as : > > foo > > It has been reported, however, that Opera does not respect > the specification, and renders it as : > > bar > > If this is the cas, would the general consensus be that this > represents a bug in the Opera rendering engine and would therefore > warrant a bug report ? I am not sure I would consider this a 'bug', rather an experimental feature. The (now marked as obsolete) css-content module allowed the content property ( with value: <string>) to be applied to any element (as opposed to only generated content pseudo elements): http://dev.w3.org/csswg/css3-content/#inserting-and-replacing-content-with-the ( I think it was also allowed in early drafts of CSS 2.0) I don't think the feature is specified in other modules, although I could have missed it. Fwiw, WebKit and Opera allow the content of any element to be replaced with a uri (e.g. an image). Barney Carroll <[email protected]> a écrit > By the by, in terms of zealous generated content as a philosophy, the > type=date inputs are another great example of Opera bringing huge > unasked-for gifts to the table. Uh? that is part of HTML5 (and actively under development for Gecko and WebKit): http://www.whatwg.org/specs/web-apps/current-work/multipage/states-of-the-type-attribute.html#date-state-(type=date) Philippe -- Philippe Wittenbergh http://l-c-n.com ______________________________________________________________________ css-discuss [[email protected]] http://www.css-discuss.org/mailman/listinfo/css-d List wiki/FAQ -- http://css-discuss.incutio.com/ List policies -- http://css-discuss.org/policies.html Supported by evolt.org -- http://www.evolt.org/help_support_evolt/
