Comment 23 for bug 24398

I agree with Mournir Lamouri that this problem is may be complicated than I first thought when I posted a duplicate bug a few years ago, and welcome his introduction of debate into this discussion

I do, however find his suggestion that websites should use autofocus unhelpful. I suspect the majority of web developers are not accessibility gurus who have the time to pay attention to issues like this.

I would like to prompt for examples where a broken refocus would cause an issue to the user.
I can think of an example where this might break the website, but doesn't affect the user much: auto-advancement to the next field when the character limit is reached in, for example, keys that are broken by spaces for ease of use (can't remember the term for this right now).

I feel the next stage of discussion should be about when and where focus can be altered by a webpage or the gui, and if we can isolate these instances if needed

One such case is password fields. I believe it is a critical security flaw that a user's password can be revealed to anyone watching the screen, be it in the workplace or over a projector screen. (@Mournir Lamouri I hope you won't suggest "learn touchtyping" :) )

Until further discussion on this issue, I move that refocussing should be disabled for password fields whilst the user is typing. Can we agree on this?