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

Re: <keygen> element

From: Maciej Stachowiak <mjs@apple.com>
Date: Wed, 02 Sep 2009 02:09:24 -0700
Cc: Jonas Sicking <jonas@sicking.cc>, Adrian Bateman <adrianba@microsoft.com>, HTML WG <public-html@w3.org>
Message-id: <0B2E10A1-0299-4890-AAD4-1EC156F37ACC@apple.com>
To: Anne van Kesteren <annevk@opera.com>

On Sep 2, 2009, at 1:39 AM, Anne van Kesteren wrote:

> On Wed, 02 Sep 2009 01:27:16 +0200, Maciej Stachowiak  
> <mjs@apple.com> wrote:
>> I agree with the last two paragraphs. I think the main thing is to  
>> provide a good crypto API so we can relegate <keygen> and browser- 
>> specific solutions to the dustbin of history.
>
> If dustbin of history means everyone removes their implementation we  
> could remove the documentation as well I suppose. However, if Gecko  
> and WebKit keep it I'm sure sites will continue to use it for one  
> reason or another and we need to have it documented.
>
> Another reason to have it in the specification is that the  
> implementation details of the element in Presto/Gecko/WebKit are  
> quite different.
>

I don't think <keygen> should be removed from anything for now; that  
was more of a rhetorical flourish than a specific technical  
recommendation. But it probably wouldn't be hard to convince sites to  
migrate to a better API if we make one. Someday it may be possible to  
completely obsolete it.

Regards,
Maciej
Received on Wednesday, 2 September 2009 09:10:06 GMT

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