Author: TomH
[Added to the original trac issue at 7.46am, Wednesday, 15th June 2011]

Changing the name isn't really very easy because the name is dictated by the automatic form handling in the application platform we use.

I mean we could do it, but then we would have to process that field manually instead of having it taken care of automatically, so I am somewhat reluctant to make the change.

Frankly for third parties to rely on the field having a particular name is just batshit crazy - it would have been far better to say that any field of a particular class would be considered to be an OpenID URL.

Author: axel[at]nennker.de
[Added to the original trac issue at 11.58am, Wednesday, 15th June 2011]

Well, the third party in this case is the form-fill component in the browser.
Form-fillers look for the id and/or name of the input field.
So if all OpenID consumers use the same name/id then the openid can be filled in by the browser; even if the user visits a site for the first time.
So I think this does make sense. Using the class attribute would be OK for browser extensions but not for the currently deployed form-fillers.

I suggest the following change:
Change the id of the input field to openid_url but not the value of the name attribute.
Change the id of the tr to prevent id clashes.

This would allow you to keep the server code as is.

-Axel

Author: TomH
[Added to the original trac issue at 1.50pm, Wednesday, 15th June 2011]

I've changed this as you suggest, and it should be live in the next half hour.