Automatic login with Opera is broken
|
thany
Joined: 2010-06-22
Posts: 26 |
Posted: Mon, 2012-06-04 11:07
|
|
When using automatic login with Opera (11.6) , the username and password get filled in and Opera immediately guesses the right button to 'click'. As long as the HTML is neat and tidy, Opera always picks the right button to click. In G3, it chooses the wrong button; it clicks the search button, and therefor never logs in using the automatic login feature. Again, this is probably not a bug in the browser. It might have to do with the fact that the login <form> gets created after the page has been loaded, confusing the browser. |
|
| Login or register to post comments |
Posts: 25945
The joys of DHTML. The password field is not populated/saved in FF either.
Some might consider this a security feature.
Dave
_____________________________________________
Blog & G2 || floridave - Gallery Team
Posts: 26
Yeah, well, since the browser stores such things in very secure places (an encrypted file inside the user profile area), the only threat is when another person gets his hands on my system login, and therefor my browser & my profile.
Anyhow, I don't think it's up to the website to (unintentionally) disable such features. And if the problems exists in FF as well, maybe you should consider a fix before someone notices the same bug in IE? ;)
(btw, we don't call it DHTML anymore, these days)
Posts: 25945
yours, but what about an internet cafe or other similar situations?
It is a bug in the browser:
If you feel it is that important feel free to submit a patch for this bug:
http://sourceforge.net/apps/trac/gallery/ticket/878
You could put the username and password in a field and hide it with css then it should be used as the fields after the modal page is rendered.
Or skip the whole modal window altogether.
Guess I'm showing my age then.
Dave
_____________________________________________
Blog & G2 || floridave - Gallery Team
Posts: 26
No, you just focus on PHP. I'm more into javascript so you could catch me calling a class an object ;)
Like I said, this is not *that* important. I though maybe you can apply a quick fix and be done with it, but if it's hard, I say skip it and wait till the browsers fix it.
Guess I was wrong