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 25326 - What is the rationale in having <keygen> as a void element? It won't be backward compatible, and in addition to this it could be used as a container for script-based legacy alternatives.
Summary: What is the rationale in having <keygen> as a void element? It won't be backw...
Status: RESOLVED WORKSFORME
Alias: None
Product: WHATWG
Classification: Unclassified
Component: HTML (show other bugs)
Version: unspecified
Hardware: Other other
: P3 normal
Target Milestone: Unsorted
Assignee: Ian 'Hixie' Hickson
QA Contact: contributor
URL: http://www.whatwg.org/specs/web-apps/...
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-04-11 13:18 UTC by contributor
Modified: 2014-04-11 14:48 UTC (History)
2 users (show)

See Also:

Attachments

Description contributor 2014-04-11 13:18:48 UTC 
Specification: http://www.whatwg.org/specs/web-apps/current-work/
Multipage: http://www.whatwg.org/C#elements-0
Complete: http://www.whatwg.org/c#elements-0
Referrer: http://www.whatwg.org/specs/web-apps/current-work/multipage/index.html

Comment:
What is the rationale in having <keygen> as a void element? It won't be
backward compatible, and in addition to this it could be used as a container
for script-based legacy alternatives.

Posted from: 94.38.225.93
User agent: Mozilla/5.0 (Windows NT 6.3; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/34.0.1847.116 Safari/537.36
Comment 1 Michael[tm] Smith 2014-04-11 13:22:25 UTC 
keygen isn't a new element. It was implemented in browsers long before it was ever specified in the HTML spec. The spec is essentially just documenting it.
Comment 2 Andrea Rendine 2014-04-11 14:48:34 UTC 
I see. Never used elements outside official guides before, so I thought it was new in implementation, as well as in specification. Thank you.