Re: removing keygen from HTML

On 2016/05/31 23:40, Harry Halpin wrote:
> On Tue, May 31, 2016 at 3:43 AM, Daniel Appelquist <[email protected]> wrote:

> My point was that the TAG should know that the W3C Web Authentication
> Working Group has started, and the W3C Web Authentication AI I believe
> fulfils most if not all of these use-cases in a way that improves on
> <keygen>, and the plan is to be in browsers by end of the year.
>
> One could argue to keep <keygen> enabled till when Web Authentication API
> is in browsers.

One could also argue that <keygen> should be available until a year or 
two after the Web Authentication API is in browsers, to give both 
browser users and application writers some reasonable time to switch 
over and avoid a flag day.

Regards,   Martin.