- From: Tab Atkins Jr. <jackalmage@gmail.com>
- Date: Wed, 23 Nov 2011 09:47:05 -0800
- To: "L. David Baron" <dbaron@dbaron.org>
- Cc: Florian Rivoal <florianr@opera.com>, www-style@w3.org
On Wed, Nov 23, 2011 at 9:37 AM, L. David Baron <dbaron@dbaron.org> wrote: > On Wednesday 2011-11-23 17:47 +0100, Florian Rivoal wrote: >> So I propose that we remove section 8 (or at least the first sentence) and >> either: >> >> * add a note that clarifies things along the line of what you >> just explained >> >> * change section 7 so that nothing ends up being a replaced element, >> and add some mechanism similar to what Tab proposed to make >> anything become a replaced element. > > My preference is the first option. > > We could also replace this sentence in section 8 (Replaced content): > > # If the computed value of the part of the ‘content’ property that > # ends up being used is a single URI, then the element or > # pseudo-element is a replaced element. > > with: > > # If the part of the ‘content’ property that ends up being used > # precedes a comma (i.e., it has additional fallback after it), > # then the element or pseudo-element is a replaced element. This seems fine. On Wed, Nov 23, 2011 at 9:33 AM, L. David Baron <dbaron@dbaron.org> wrote: > On Wednesday 2011-11-23 08:40 -0800, Tab Atkins Jr. wrote: >> Not WebKit. We currently make "div { content: url(foo); }" turn the >> div into a replaced element. > > But only if it's on an element and not on a pseudo-element? Yup. On a pseudo, "content: url(foo);" makes an anonymous inline. But we're the only one that has the normal-element behavior, so we could likely change it. ~TJ
Received on Wednesday, 23 November 2011 17:47:53 UTC