Re: removing keygen from HTML

On Tue, 31 May 2016 16:40:30 +0200, Harry Halpin <[email protected]>  
wrote:

> On Tue, May 31, 2016 at 3:43 AM, Daniel Appelquist <[email protected]> wrote:
>
>> Hi Folks - the TAG (in the person of Travis) has written on this topic:
>>
>> https://w3ctag.github.io/client-certificates/#replacing-keygen
>>
>> As noted, it represents the rough consensus of the TAG on this issue.

As I read that, in relation to the question facing the Web Platform group  
for the HTML spec:
  1) It doesn't present any urgency to remove keygen, noting that there is  
not a replacement available now.
  2) I don't know how rough that consensus is. Multiplying rough consensus  
by rough consensus can quickly get to "a minority opinion".

> One could argue to keep <keygen> enabled till when Web Authentication API
> is in browsers.

Which would have a critical impact on our current question - should we  
remove it *now*?

> Also, as <keygen> is currently non-interoperable and specified in only  
> one browser

As far as I can see it works in Safari as well. Is my simplistic testing  
giving a false positive, or does it work?

>> On Tue, 31 May 2016 at 13:33 Eric Mill <[email protected]> wrote:
>>
>>> The original email said: "Since the TAG, or its members, appear to have
>>> opinions about our spec, we'd be grateful to hear them." It'd be most
>>> productive for this thread's discussion to at least be initiated by a
>>> member of the TAG.

To be fair, I understand the nature of this mailing list, and while I  
addressed my comments prmiarily to the TAG I am grateful for others giving  
input too.

cheers

Chaals

-- 
Charles McCathie Nevile - web standards - CTO Office, Yandex
  [email protected] - - - Find more at http://yandex.com