W3C home > Mailing lists > Public > public-html-admin@w3.org > February 2013

[Bug 20861] New: Should <keygen> be conforming-but-obsolete

From: <bugzilla@jessica.w3.org>
Date: Mon, 04 Feb 2013 13:44:02 +0000
To: public-html-admin@w3.org
Message-ID: <bug-20861-2495@http.www.w3.org/Bugs/Public/>
https://www.w3.org/Bugs/Public/show_bug.cgi?id=20861

            Bug ID: 20861
           Summary: Should <keygen> be conforming-but-obsolete
    Classification: Unclassified
           Product: HTML WG
           Version: unspecified
          Hardware: PC
                OS: All
            Status: NEW
          Severity: normal
          Priority: P2
         Component: HTML5 spec
          Assignee: robin@w3.org
          Reporter: robin@w3.org
        QA Contact: public-html-bugzilla@w3.org
                CC: mike@w3.org, public-html-admin@w3.org,
                    public-html-wg-issue-tracking@w3.org

It would appear that <keygen> could be a good candidate for filing under that
category as it seems clear that at least one browser plans to never have any
useful behaviour for it (beyond the required parsing/DOM) so that I don't
believe we ever want new content to be using it.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
Received on Monday, 4 February 2013 13:44:03 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Monday, 4 February 2013 13:44:03 GMT