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

Re: foo {content:title} - a proposal

From: Leif Halvard Silli <xn--mlform-iua@xn--mlform-iua.no>
Date: Wed, 13 Mar 2013 16:21:14 +0100
To: James Craig <jcraig@apple.com>
Cc: Steve Faulkner <faulkner.steve@gmail.com>, "www-style@w3.org" <www-style@w3.org>, "wai-xtech@w3.org" <wai-xtech@w3.org>, Leif Halvard Silli <xn--mlform-iua.no@xn--mlform-iua.no.no>
Message-ID: <20130313162114951231.122674dd@xn--mlform-iua.no>
Yes. In Webkit. But it isn’t my impression that we are moving towards a 
situation where *more* user agents support generated content for void 
elements. Am I wrong? Opera used to have the best support for generated 
content on void elements - <input> and <img>. But then they willfully 
disabled much of what they could do, in order to conform to CSS 2.1 - 
or what do I know why they did it. And, since I some Opera engineers 
info gave me that info, they have "disabled" their entire rendering 
engine. There is no progress in Firefox and IE, that I am aware of. 

Thus, the generated content field for void elemnets seems to me like a 
where the only that is moving, is Webkit. Perhaps one could bring more 
vendors along with a content:title; ? 

Leif H Silli

James Craig, Wed, 13 Mar 2013 08:04:47 -0700:
> Leif, can’t you already do what you’re asking for with this syntax?
> 
> input:focus::after { content: attr(title); }
> 
> On Mar 13, 2013, at 3:42 AM, Steve Faulkner 
> <faulkner.steve@gmail.com> wrote:
> 
>> Leif wrote:
>>  
>>> Motivation: Since the <label> example above isn’t keyboard accessible
>>> today, Steve is proposing to change the HTML5 spec.[1]
>>> 
>>> [1] http://lists.w3.org/Archives/Public/public-html/2013Mar/0084

>> 
>> Please note: 
>> 
>> I am only proposing a change to author advice/requirements to match 
>> current, foreseeable future and historical user agent implementation 
>> realities.
>> 
>> 
>> 
>> with regards
>> 
>> SteveF
>> --
>> HTML 5.1
>> 
>> 
>> On 13 March 2013 05:55, Leif Halvard Silli 
>> <xn--mlform-iua.no@xn--mlform-iua.no.no> wrote:
>>> Dear CSS Working Group,  (with CC to wai-xtech@w3.org)
>>> 
>>> According to HTML5, the title attribute in the following <label>
>>> element example, applies to each of <label>’s child elements as well:
>>> 
>>>   <label title="Advisory text.">
>>>      <input type="text" />
>>>      <span></span>
>>>   </label>
>>> 
>>> Thus, imagine that, in order to display the title 'inside' the <input>
>>> element, one could do this:
>>> 
>>>     input:focus::after { content:title; }
>>> 
>>> Or, more realistically (given all the problems with generated content
>>> for void elements), that we could render the title inside the <span>
>>> element, when <input> has focus:
>>> 
>>>     input:focus + span::before { content:title; }
>>> 
>>> Result, from CSS consumer’s point of view:
>>> 
>>>   <label title="Advisory text.">
>>>      <input type="text" />
>>>      <span><::before>Advisory text</::before></span>
>>>   </labebl>
>>> 
>>> Since all browsers have a method for knowing what each element’s title
>>> is, perhaps this proposal isn’t so off?
>>> 
>>> Motivation: Since the <label> example above isn’t keyboard accessible
>>> today, Steve is proposing to change the HTML5 spec.[1]
>>> 
>>> [1] http://lists.w3.org/Archives/Public/public-html/2013Mar/0084

>>> --
>>> leif halvard silli
>> 
Received on Wednesday, 13 March 2013 15:21:51 GMT

This archive was generated by hypermail 2.3.1 : Tuesday, 26 March 2013 17:21:06 GMT