263129 - Ignore focus() in onload if I've already focused something

Status: RESOLVED DUPLICATE of bug 226386

(Toolkit :: Form Manager, enhancement)

Description

[Dennis Körner]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; rv:1.7.3) Gecko/20040913 Firefox/0.10.1
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; rv:1.7.3) Gecko/20040913 Firefox/0.10.1

When entering username and password on https://webmail.1und1.de before the page
has been completely loaded and sending through pressing Enter the focus will be
set to the username

If your fast, that means that the username will be your username plus a part of
your password

Reproducible: Always
Steps to Reproduce:
1.
2.
3.

Comment 1

[Peter van der Woude [:Peter6]]

WONT ?

Comment 2

[Jesse Ruderman]

I agree with Peter6 that there won't be an option for this.  How about changing
the summary to "Ignore focus() in onload if I've already focused something"?

Comment 3

[Dennis Körner]

works for me... changed

Comment 4

[Stasys Adiklis]

This is a dupe of bug 124750. See comment #107 there.

Comment 5

[Stasys Adiklis]

Sorry, it's not a dupe of the bug 124750. In comments 109 and 110 they claim
that its a feature... which is something i disagree with.

Comment 6

[Thomas Dalton]

It's a feature.  It may not be a good one, but we have to do what the page tells
us to - that's the whole point of standards.

Resolve WONTFIX?

Comment 7

[Stasys Adiklis]

> It's a feature.  It may not be a good one, but we have to do what the page tells
> us to - that's the whole point of standards.

Of course you should do what the page tells. But what if user has better idea
than a page and focused to a field of interest while page was still loading?

I don't see how implementation of this RFE would interfere with standards.
Unless you can point me to a part of a standard which demands wrestling with
user actions.

Comment 8

[Thomas Dalton]

The problem is with expectations.  If the person making the page expects their
focus() command to work they might rely on it.  For example they might use when
focus is lost to that field for validation.  They should check again when they
submit, but many people are lazy and it seems better to stick with what they expect.

On the other hand, it really annoys me when sites do this and I would like it
stopped... maybe evangelism would be a better solution?

Comment 9

[Stasys Adiklis]

> On the other hand, it really annoys me when sites do this and I would like it
> stopped... maybe evangelism would be a better solution?

If you ask me, i'd like the feature burried under about:config. So that geeks,
who know what they are doing, could enable it.

OTOH if you make this feature accessible by all (via Options dialog) and maybe
even ON by default, then maybe breakage of functionality of those sites by this
option will actually work better than "evangelism"?

Comment 10

[Thomas Dalton]

A large majority of people never change the options, so you can assume everyone
will be using whatever is the default.  If we decide that the default should be
to ignore focus() commands then it's the same as ignoring them regardless of
user preference as far as web designers are concerned.

I don't think something in the options panel is a good idea - most people don't
know what "focus" means, how would we phrase the option?  Something in
about:config is a good idea though.  We just have to decide on the default. 
Default to ignore and let geeks change it to fix broken sites if they need to,
or default to allow and let geeks change it if they get too annoyed.  What is
the most desired behaviour for non-geek users?  Sites that work or sites that
don't annoy you?

Comment 11

[timeless]

while the summary request is not presently possible, you should be able to
disable all calls to focus today using caps (too bad it would trigger an
exception) - which you could create using about:config (although you cannot
review them there).

Comment 12

[Gervase Markham [:gerv]]

This is an automated message, with ID "auto-resolve01".

This bug has had no comments for a long time. Statistically, we have found that
bug reports that have not been confirmed by a second user after three months are
highly unlikely to be the source of a fix to the code.

While your input is very important to us, our resources are limited and so we
are asking for your help in focussing our efforts. If you can still reproduce
this problem in the latest version of the product (see below for how to obtain a
copy) or, for feature requests, if it's not present in the latest version and
you still believe we should implement it, please visit the URL of this bug
(given at the top of this mail) and add a comment to that effect, giving more
reproduction information if you have it.

If it is not a problem any longer, you need take no action. If this bug is not
changed in any way in the next two weeks, it will be automatically resolved.
Thank you for your help in this matter.

The latest beta releases can be obtained from:
Firefox:     http://www.mozilla.org/projects/firefox/
Thunderbird: http://www.mozilla.org/products/thunderbird/releases/1.5beta1.html
Seamonkey:   http://www.mozilla.org/projects/seamonkey/

Comment 13

[Jesse Ruderman]

*** Bug 243129 has been marked as a duplicate of this bug. ***

Comment 14

[Ricardo Garcia]

Hello, I'm the one who reported bug 243129 and I just read all the comments in
here. My bug report was more restricted than this one, but I still think it
raises a valid point in this discussion. I would restrict ignoring the onload
focus only when you are inside a password field. That is the only dangerous
situation. Other situations may be annoying, but probably not dangerous.

Comment 15

[Boris Zbarsky [:bzbarsky]]

*** This bug has been marked as a duplicate of 226386 ***