Why does it still focus on the namefield even when it is not blank? If the admin's already logged into the board but they don't have an active ACP session, it would make more sense to populate the namefield box and focus the password box.

I don't get what you're saying. :blink:

Could you elaborate a little?

1. Log into your test board.
2. Click Admin CP.
3. You'll see that it focuses on the namefield textbox even though it's already been filled in automatically. It would make more sense to focus the password textbox in this scenario.

Of course, if the member ID wasn't recognised and the namefield textbox is blank, it should be focused.

All it really needs is an if statement checking namefield is empty. If not, focus the password textbox. If so, focus the namefield.

Hope I'm expressing myself satisfactorily >_<

It would make more sense to focus on the submit button so then you can just hit enter and off you go. (That is, if both fields were filled.)

It would make more sense to focus on the submit button so then you can just hit enter and off you go. (That is, if both fields were filled.)

*headdesk*

OK. An admin logs into the board. They don't have an active ACP session yet, but they're logged into the main board.

Then, they decide to click Admin CP. They are taken to the ACP login screen and it recognises that they are logged in already, but it needs their password to start an admin session.

So, even though all it needs is their password, the javascript that is presently there will always focus the namefield (username) box. Back in the days of 2.0, I think it would focus the password box if the username was already recognised, and if not, it would just focus the namefield box.

It's not a major thing, just a minor inconvenience to have to hit tab or click or whatever 99% of the time (at least, I personally usually only access the ACP when I'm already logged into the main board).

Note the part that said

(That is, if both fields were filled.)

Note the part that said

You should never need to focus on a submit button. The Enter key should submit a form regardless of what you have focused at the time.

Ok well I didn't know that. Anyway, although your idea is ok, it seems a little stupid. Reason being is that it only takes some 2 seconds to either hit tab, or click the mouse into the password field. It's not that big of a deal...

Ok well I didn't know that. Anyway, although your idea is ok, it seems a little stupid. Reason being is that it only takes some 2 seconds to either hit tab, or click the mouse into the password field. It's not that big of a deal...

As I've already said myself, it's hardly major. Just makes no sense considering they got this time-saving feature completely right in 2.0, then missed it out in 2.1, and now they've put it back but done it slightly wrong :)

Note the part that said

Both fields will never, EVER, be automatically filled in a stock (or rather, sane) install.

I agree, and this was done prior to 2.2