This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 7499 - <keygen> should not be defined as a requirement for a conforming HTML5 user agent and should be removed from the spec
Summary: <keygen> should not be defined as a requirement for a conforming HTML5 user a...
Alias: None
Product: HTML WG
Classification: Unclassified
Component: pre-LC1 HTML5 spec (editor: Ian Hickson) (show other bugs)
Version: unspecified
Hardware: All All
: P2 major
Target Milestone: LC
Assignee: Ian 'Hixie' Hickson
QA Contact: HTML WG Bugzilla archive list
Keywords: NE, NoReply
Depends on:
Blocks: 7480
  Show dependency treegraph
Reported: 2009-09-04 16:15 UTC by Adrian Bateman [MSFT]
Modified: 2010-10-04 13:57 UTC (History)
3 users (show)

See Also:


Description Adrian Bateman [MSFT] 2009-09-04 16:15:36 UTC

Adrian Bateman wrote:
> On Wednesday, September 02, 2009 12:12 PM, Maciej Stachowiak wrote:
>> (Note: if <keygen> is removed from HTML5 itself, it should probably
>> go in a separate spec, since non-IE browsers do have to implement
>> it and interoperability needs to be improved.)
> In particular, this is my request. It should be documented but not in
> HTML5 itself - the HTML5 spec supports loading unknown elements that
> are defined elsewhere [1]. Since it wasn't included in previous
> versions of HTML and the desire is not to include it in future
> versions, not adding it at this stage seems preferable.
> [1]

<keygen> has a number of issues that means it doesn't meet the needs of the majority of web developers. <keygen> wasn't previously part of HTML and rather than creating an instant legacy problem, it's use should be defined in another document for those vendors who wish to support it interoperably for historical reasons.
Comment 1 Ian 'Hixie' Hickson 2009-09-14 10:27:20 UTC
I've made the encryption parts of <keygen> optional.
Comment 2 Maciej Stachowiak 2010-03-14 14:50:38 UTC
This bug predates the HTML Working Group Decision Policy.

If you are satisfied with the resolution of this bug, please change the state of this bug to CLOSED. If you have additional information and would like the editor to reconsider, please reopen this bug. If you would like to escalate the issue to the full HTML Working Group, please add the TrackerRequest keyword to this bug, and suggest title and text for the tracker issue; or you may create a tracker issue yourself, if you are able to do so. For more details, see this document:

This bug is now being moved to VERIFIED. Please respond within two weeks. If this bug is not closed, reopened or escalated within two weeks, it may be marked as NoReply and will no longer be considered a pending comment.