W3C home > Mailing lists > Public > www-style@w3.org > January 2013

RE: Styling HTML placeholder attribute

From: Sylvain Galineau <sylvaing@microsoft.com>
Date: Thu, 24 Jan 2013 20:30:58 +0000
To: Tab Atkins Jr. <jackalmage@gmail.com>, Brad Kemper <brad.kemper@gmail.com>
CC: Arron Eicholz <Arron.Eicholz@microsoft.com>, Mounir Lamouri <mounir@lamouri.fr>, www-style list <www-style@w3.org>, "Lea Verou (leaverou@gmail.com)" <leaverou@gmail.com>
Message-ID: <3C4041FF83E1E04A986B6DC50F0178291BF4AC5B@TK5EX14MBXC221.redmond.corp.microsoft.com>

[Tab Atkins Jr.:]
> I'm arguing against Arron and Sylvain's assertions that we should decide,
> from a theoretical perspective, whether to address placeholder styling
> with a pseudoclass or pseudo-element, and then after making that decision,
> decide on the styling.

This a straw man. This whole part of the discussion started with your claim
that a pseudo-element is 'definitely better' as opacity would otherwise
be awkward as a default style. We don't believe this is a sufficient reason 
to require all browsers to add a pseudo-element, never mind requiring authors to
deal with one. Especially when it doesn't address other interesting scenarios
and user requests. 

We also believe that if opacity requires extra pseudo-elements to work right 
then *maybe* opacity has a problem that needs fixing. Is that 'theoretical'?

There is nothing 'theoretical' about any of this. I have spent an entire 
release working on control styling and the feedback thereof. Believe me, 
it's quite real. And that experience motivates a strong desire to think 
about the use-case from a more general perspective  than 'Opacity! 
Opacity! But what about opacity? We must have opacity!'. But somehow, 
the latter is the approach focused on users' concerns and the former
is 'architecture astronautics'. 

Clearly, this won't get anywhere. Oh well.
Received on Thursday, 24 January 2013 20:32:04 UTC

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