W3C home > Mailing lists > Public > public-html@w3.org > September 2009

Re: <keygen> element

From: Sam Ruby <rubys@intertwingly.net>
Date: Sun, 06 Sep 2009 06:58:41 -0400
Message-ID: <4AA395E1.3070609@intertwingly.net>
To: Maciej Stachowiak <mjs@apple.com>
CC: Jonas Sicking <jonas@sicking.cc>, Ian Hickson <ian@hixie.ch>, Anne van Kesteren <annevk@opera.com>, Lachlan Hunt <lachlan.hunt@lachy.id.au>, HTML WG <public-html@w3.org>
Maciej Stachowiak wrote:
> 
> On Sep 5, 2009, at 8:26 PM, Jonas Sicking wrote:
> 
>> Putting just the <keygen> element, but none of the actual
>> functionality, thus allowing microsoft (or anyone else) to just
>> implement a very small amount of stubbed code seems like a political
>> solution. It wouldn't actually help any website authors, and it would
>> force UAs to still implement (and test) the stubbed code.

I agree with this perspective.

Bug 7499 captures the requirement: "<keygen> should not be defined as a 
requirement for a conforming HTML5 user agent".  It then goes further 
and states "and should be removed from the spec" -- this second part is 
just one possible way to satisfy the requirement.

 From a technical perspective, what the current spec states is not 
something that every browser with non-trivial market share intends to 
implement.  That's the problem to be solved.

>> Is there a reason we couldn't mark <keygen> conforming but
>> obsolete/deprecated? All UAs seem to want to deprecate and replace
>> (thus remove) the feature. Saying that it's obsolete and/or deprecated
>> would seem to reflect that fairly well.
> 
> Marking it obsolete or deprecated would still make it required for IE to 
> implement. (All current obsolete features in HTML5 are mandatory for 
> implementations.) Do you think they should be allowed to not implement it?

I agree that obsolete or deprecated would not be sufficient.  It could 
be done in addition to making it optional, but not instead of.

> What marking it obsolete would do is result in a conformance error on 
> every page using it - this seems orthogonal to Microsoft's concern, and 
> at least to me it seems unhelpful. But perhaps you have some different 
> concerns that would be addressed by making keygen obsolete.

While error might be overkill, unless the expectation is that this 
element will be universally implemented, a warning does seem in order.

>  - Maciej

- Sam Ruby
Received on Sunday, 6 September 2009 10:59:40 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Wednesday, 9 May 2012 00:16:48 GMT