Re: HTML5 design philosophy disconnect

Hi Ryosuke,

> Just because something is in the spec doesn't mean all UAs get it right.

I am well aware of this, it would be good for developers and users, if
features that have been in the language for an extended period have
their lack of implementation acknowledged.

> If some UA doesn't support a particular feature and it's important for you,
> then please contact the vendor. WebKit is open sourced and we welcome
> almost anyone to file bugs. I'm sure other vendors would love to get
> feedback
> from users and authors as well.

I do so on a regular basis, here is the bug i filed on this issue for
chrome, back in Feb 2011.
http://code.google.com/p/chromium/issues/detail?id=71933


regards
Stevef

On 6 January 2012 18:35, Ryosuke Niwa <rniwa@webkit.org> wrote:
> On Fri, Jan 6, 2012 at 3:18 AM, Steve Faulkner <faulkner.steve@gmail.com>
> wrote:
>>
>> One example (there are many more),
>> The use of implicit labels is found in examples in the HTML5 spec,
>> something that has been a documented feature of HTML since at least 24
>> December 1999, yet at least one major browser has not implemented
>> accessibility support for it yet. [1]
>
>
> Just because something is in the spec doesn't mean all UAs get it right.
> Each UA has its own priorities to fix bugs and add features. For the example
> you pointed out, we seem to have a tracking bug: https://webkit.org/b/69736
>
>> So we have a method that has been promoted for 10 years and continues
>> to be promoted which is broken, how is that useful for either users or
>> developers?
>
>
> If some UA doesn't support a particular feature and it's important for you,
> then please contact the vendor. WebKit is open sourced and we welcome
> almost anyone to file bugs. I'm sure other vendors would love to get
> feedback
> from users and authors as well.
>
> Best regards,
> Ryosuke Niwa
> Software Engineer
> Google Inc.
>

Received on Friday, 6 January 2012 21:38:31 UTC