Re: Call for Consensus - Remove <keygen> from HTML

+1 for removal


On 2016-05-30 13:15, John Foliot wrote:
> +1 to the removal
>
> JF
>
> On Mon, May 30, 2016 at 10:22 AM, Dylan Barrell 
> <dylan.barrell@deque.com <mailto:dylan.barrell@deque.com>> wrote:
>
>     +1
>
>     > On May 30, 2016, at 5:55 AM, Chaals McCathie Nevile
>     <chaals@yandex-team.ru <mailto:chaals@yandex-team.ru>> wrote:
>     >
>     > Dear all, given insufficient response to declare a consensus, I
>     am holding this call open until end of day 31 May.
>     >
>     > cheers
>     >
>     > Chaals
>     >
>     >> On Sat, 21 May 2016 14:24:26 +0200, Chaals McCathie Nevile
>     <chaals@yandex-team.ru <mailto:chaals@yandex-team.ru>> wrote:
>     >>
>     >> Dear all,
>     >>
>     >> this is a call for consensus on the proposal
>     >>
>     >>  The keygen element should be removed from the HTML 5.1
>     specification.
>     >>
>     >> This is to resolve issue #43
>     https://github.com/w3c/html/issues/43 - the result would be along
>     the lines of pull request 354: https://github.com/w3c/html/pull/354
>     >>
>     >> Please provide a response before the end of the day May 29.
>     Silence will be considered acceptance of the proposal, but an
>     explicit response is preferred.
>     >>
>     >> There have been various discussions elsewhere, and the links
>     from the issue give more detail. Broadly, the motivation for
>     removal is poor interoperability in the modern web, poor
>     suitability for purpose, and likely deprecation or removal from
>     browsers.
>     >>
>     >> cheers
>     >>
>     >> Chaals
>     >
>     >
>     > --
>     > Charles McCathie Nevile - web standards - CTO Office, Yandex
>     > chaals@yandex-team.ru <mailto:chaals@yandex-team.ru> - - - Find
>     more at http://yandex.com
>     >
>
>
>
>
> -- 
> John Foliot
> Principal Accessibility Consultant
> Deque Systems Inc.
> john.foliot@deque.com <mailto:john.foliot@deque.com>
>
> Advancing the mission of digital accessibility and inclusion