This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
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.
But that's because existomg code relies on the UA being *either* IE (-> ActiveX) or having <keygen> support, no?
(In reply to comment #1) > But that's because existomg code relies on the UA being *either* IE (-> > ActiveX) or having <keygen> support, no? Right, but that changes nothing if the idea is that new content should not use it. Filing it as obsolete doesn't remove the existing support that relies on it, it just makes it clear that new stuff shouldn't use it.
So does the spec tell authors what to use *instead*? (/me no crypto expert, just wondering whether we made progress since this came up years ago)
(In reply to comment #3) > So does the spec tell authors what to use *instead*? > > (/me no crypto expert, just wondering whether we made progress since this > came up years ago) Eventually, the Web Cryptography API https://dvcs.w3.org/hg/webcrypto-api/raw-file/tip/spec/Overview.html though at this point we need to get implemented in more UAs
I came here to make the comments Julian already made. (In reply to comment #4) > Eventually, the Web Cryptography API > https://dvcs.w3.org/hg/webcrypto-api/raw-file/tip/spec/Overview.html though > at this point we need to get implemented in more UAs That doc says key provisioning is out of scope. <keygen> is used for CA enrollment processes. I think we should not obsolete it without a replacement.
(In reply to Henri Sivonen from comment #5) > I came here to make the comments Julian already made. > > (In reply to comment #4) > > Eventually, the Web Cryptography API > > https://dvcs.w3.org/hg/webcrypto-api/raw-file/tip/spec/Overview.html though > > at this point we need to get implemented in more UAs > > That doc says key provisioning is out of scope. <keygen> is used for CA > enrollment processes. > > I think we should not obsolete it without a replacement. Agreed, so moving this to resolved=wontfix. There's been no new information on this in 2+ years and it does not seem important enough to merit being kept open for another N years with nothing happening. I can of course be re-opened if anything has changed.