W3C home > Mailing lists > Public > public-html@w3.org > April 2010

Re: native elements versus scripted

From: Shelley Powers <shelley.just@gmail.com>
Date: Tue, 6 Apr 2010 12:28:31 -0500
Message-ID: <x2h643cc0271004061028n86860c2dldf2e4efe70fab1f1@mail.gmail.com>
To: HTMLWG WG <public-html@w3.org>
Sorry, I keep thinking of these after I hit send!

And if we assume built in accessibility in the control, and don't
provide alternative ARIA markup in the element, we could lose
accessibility if the HTML5 element isn't implemented yet.

Shelley


On Tue, Apr 6, 2010 at 12:27 PM, Shelley Powers <shelley.just@gmail.com> wrote:
> On additional correction to this addendum.
>
> The downside to this is that if the browser doesn't implement the
> control, that's how the field will be designed, which will most likely
> make it oddly different than other fields in the form.
>
> Shelley
>
>
> On Tue, Apr 6, 2010 at 12:24 PM, Shelley Powers <shelley.just@gmail.com> wrote:
>> I did want to add an addendum and clarification.
>>
>> Mike Taylor (http://twitter.com/miketaylr) pointed out to me on
>> Twitter[1] that we can use the CSS selectors to provide some overall
>> styling for the new elements, such as using the following:
>>
>> (css) [type=date] {font: bold 42px 'Hobo Std';color:orangered;}
>>          <input type="date">
>>
>> We can't style the individual components of the objects that open, but
>> we can "cast" a general setting on the overall element, which is
>> inherited by the opened control. I'm assuming this presentational
>> behavior will apply to the other browsers, too.
>>
>> Shelley
>>
>> [1] http://twitter.com/miketaylr/status/11708590365
>>
>
Received on Tuesday, 6 April 2010 17:29:04 UTC

This archive was generated by hypermail 2.3.1 : Monday, 29 September 2014 09:39:16 UTC