Last modified: 2014-06-17 17:02:32 UTC
Hello, I recently introduced a new and innovative feature in the user interface, which I (until now) only used for my own projects which you cannot know: when users move the mouse over a field which can get the focus - for example the search input field - this elements gets the focus automatically on mouseover selection.mouseover(function(){$(this).focus()}) I introduced this in rev89950 for the search field of E:Vector, you can fetch the version and try it. I am interested in reasoned statements, why this is a "must have" or "nogo. not in conformity to vintage user interfaces". Personally, I changed really all my applications to this "new" style, but I prefer it. It saves mouse _clicks_.
I *like* that. You need simply to get used to it (in that respect I accept all objection under the title "user are not yet get used to it" Let's try it !
I think it's completely counter-intuitive. When I mouseover a textbox/textarea/etc I do not--as a user--expect them to be automatically selected for me. It may save some keystrokes if you're familiar with the application at hand (in your case: your own projects you wrote yourself), but I think it would be highly confusing to people who aren't expecting the behavior.
(In reply to comment #2) > I think it's completely counter-intuitive. When I mouseover a > textbox/textarea/etc I do not--as a user--expect them to be automatically > selected for me. > > It may save some keystrokes if you're familiar with the application at hand (in > your case: your own projects you wrote yourself), but I think it would be > highly confusing to people who aren't expecting the behavior. please try it LIVE on http://www.translatewiki.net
(skin Vector needed)
Please let me state again: _all_ other elements must fetch the focus (back) again. This is very easy to achieve. Sorry, when I introduced something, which might be too innovative for the majority.
"Vintage"? "Innovative"? It's possible that your bias may be more transparent than you think. Focus is an important part of a user interface, not an annoyance that needs to be "magically" done away with. Mouse hovering should never select something or change focus, anything to the contrary is highly likely to present mode errors[1]. This is not something new at all. The concept of explicit change of focus is not an artifact from the old days, in fact, it's much the other way around[2]. Please just let this go. [1] http://en.wikipedia.org/wiki/Mode_(computer_interface)#Mode_errors [2] http://en.wikipedia.org/wiki/X_Window_System#Computer_accessibility_related_issues
LATER: to be fair and give innovation a chance.
You may as well mark it whatever you like, you are clearly unwilling to listen to anyone and have chosen this obscure feature request as your new hobby.
We would definitely never do this; it's inconsistent with standard user interfaces and interferes with expected mouse and keyboard behavior.
Interface element activation should only ever happen through direct user will and agency. Highlighting an element to indicate that it can be interacted with on mouseover is fine; focusing on that element is NEVER okay. Consider the following: I select the editor pane. I start typing. I move the mouse out of the way. Now I am suddenly typing into the search box. Unexpected and unwelcome.
The question is how to remove it from TWN? It's helluva annoying.
(In reply to comment #11) > The question is how to remove it from TWN? It's helluva annoying. Don't be worry: this will be done when a new version from trunk is checked out: the maintainers do this regularly. currently TWN runs r90142 (10 hours lag).
(In reply to comment #11) > The question is how to remove it from TWN? It's helluva annoying. The auto-focus on mouseover has been reverted in r90186 (TWN is currently at r90142 , this means that you can expect this change becoming effective in about one day or sooner.
