Xojo Uses very unique names for Fields in a browser.
They appear to be generated on the fly by the server. This is Uber cool for security.
But it breaks the browser ability to store a password. (Or other fields)
Has anyone come up with a work around for this?
Xojo uses unique IDs, but the field name attributes are very specifically left the way you name them in the IDE and that’s usually what the PMs key off of.
We tested this with several password managers and they all seemed to work when we made this fix last summer.
Weren’t you the one that filed the original bug report?
Cool.
Are you saying the answer is as simple as using the name: PASSWORD instead of WebtextField_Password ?
Whatever you name your field is the name that will be used in HTML and by the password managers, yes.