W3C home > Mailing lists > Public > www-style@w3.org > August 2014

Re: [css-images][selectors][css21] ::before and ::after on replaced elements

From: Brad Kemper <brad.kemper@gmail.com>
Date: Mon, 25 Aug 2014 07:57:18 -1000
Message-Id: <7FB370A9-46DA-41EA-B9A0-A3106AAF5CDB@gmail.com>
Cc: Florian Rivoal <florian@rivoal.net>, www-style list <www-style@w3.org>
To: "Tab Atkins Jr." <jackalmage@gmail.com>

> On Aug 21, 2014, at 2:05 PM, "Tab Atkins Jr." <jackalmage@gmail.com> wrote:
> 
>> On Thu, Aug 21, 2014 at 3:40 PM, Florian Rivoal <florian@rivoal.net> wrote:
>> On Fri, 22 Aug 2014 00:21:10 +0200, Tab Atkins Jr. <jackalmage@gmail.com>
>> wrote:
>>> While we definitely need to figure out something for this eventually,
>>> reinterpreting ::before/after as siblings is definitely not the right
>>> idea.  We'll likely eventually add something that adds siblings for
>>> all elements.
>> 
>> So we should:
>> (1) stick to the fact that ::before/::after on replaced elements do nothing
>> and
>> (2) eventually spec something like ::sibling-before/::sibling-after
>> 
>> That would make sense to me, and I don't see any reason to wait to put (1)
>> in a spec explicitly. Since the selector spec is the one refering to 2.1,
>> which says we will eventually say how this work, it looks like a good
>> place for a clarification. How about this at the end of section 3.7:
>> 
>>  Note. Since ::before and ::after add children to the originating
>>  element, they have no effect on replaced elements such as the HTML img
>>  element.
> 
> The reason we haven't done this yet is that browsers aren't that
> simple.  We have "semi-replaced" elements, such as form inputs, which
> are considered "replaced" by CSS, but which react to styling as if
> they had children in several browsers.  In particular, most inputs
> allow ::before/::after to be used.

When you say "most inputs" are you talking about <input> elements, such as with 'input[type=text]::before'? I didn't think that would work. Or do you mean things like 'textarea::before' and 'button::before'?

> Once we come up with a story for form styling, such that we can
> actually define the set of "really replaced" elements, I'm happy to
> add wording that says that ::before and ::after don't apply to them.

Can we just say that ::before and ::after do not apply to elements that cannot have children in the markup language? That would also include BR, HR, LINK, etc. that are not replaced elements.
Received on Monday, 25 August 2014 17:58:06 UTC

This archive was generated by hypermail 2.4.0 : Friday, 25 March 2022 10:08:45 UTC