Re: <keygen> element

I'm assuming by "issue" you mean the objection raised to <keygen> by  
Microsoft.

On Sat, 05 Sep 2009 14:22:25 +0200, Sam Ruby <rubys@intertwingly.net>  
wrote:
> Renaming the element to follow HTML5's advice would address this issue.

This would not address the issue unless you mean to also remove the  
element from HTML5. However it is pretty clear that browsers cannot rename  
the element so I'm not sure why this is being suggested.


> Marking it as proprietary or obsolete (bug 7480) would address this  
> issue.

Even obsolete elements still need to be supported by browsers so this is  
not a solution to the issue for Microsoft.


> Defining it in a separate document (bug 7499) would address this issue.

Agreed.


> Coming up with something better that everyone would be willing to adopt  
> (any ideas?) would address this issue.

I don't see how this would address the issue unless we somehow also  
convince all the sites that use <keygen> to no longer use it and convince  
the browsers that implement <keygen> to remove support for it.


> I don't believe that we will find consensus on retaining keygen as  
> currently specified in the HTML5 draft.

I'm still hopeful and am not convinced this needs to be addressed before  
Last Call.


> What issue do you, Anne, have with putting this element in a separate  
> document and clearly indicating that it is an optional feature that a  
> number of browser vendors have implemented, and new user agents should  
> consider should they happen to have similar requirements?

I don't necessarily have an issue with putting this into a separate  
document. I'm not sure about all the other clauses you attach to that  
though.


-- 
Anne van Kesteren
http://annevankesteren.nl/

Received on Saturday, 5 September 2009 12:40:09 UTC