Search bar has ClickSelectsAll behavior
Categories
(Firefox :: Address Bar, defect)
Tracking
()
People
(Reporter: u683078, Unassigned)
Details
User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:73.0) Gecko/20100101 Firefox/73.0
Steps to reproduce:
Try to edit search bar content. 1000 times a day!
Actual results:
Hole field get selected
Expected results:
Put cursor at position where i clicked.
I know this issue has addressed meany times before, specially for the URL Bar. I read them al. But seams that developers not realizes how frustrating it is for user who edit content on URL or search bar al the time. Just make it optional as it was. This is such an common GUI element that is has to work flawless for everyone. So many people, so many wishes. Don't try to force them to one system. People will make some day a forke of it and start their own browser. Honor Firefox its reputation for most customizable browser. Make this behavior optional, please!
|
||
Comment 1•5 years ago
|
||
The Bugbug bot thinks this bug should belong to the 'Firefox::Address Bar' component, and is moving the bug to that component. Please revert this change in case you think the bot is wrong.
|
||
Comment 2•5 years ago
|
||
This was an intentional change, I'll mark the report as feedback.
@Marco Bonardo
It is clear you really like the ClickSelectAll behavior. You argue for it in many ways to keep it this way. Many of your arguments can easily refuted but you consistently fighting against the will of users that clearly prefer another workflow. Arguments like hard-to-test and cross-platform universal are so weak that they can easily be undermined with many examples and counter-arguments. But more discussion on this topic is hard to come by because every time it is silenced by labeling it as WON't fix.
Among dozens of others preferences that are still configurable, this one should and will be banned by developers. I don't get it. But hope that enough people will make themselves heard so that it becomes clear one day.
|
|
||
Comment 4•5 years ago
|
||
I'm sorry but this is not a personal opinion, I'm just reporting the underlying decision that came out of a process involving various stakeholders. If such decision will change, I will gladly report that as well.
Its also up to you to report back this tip of the iceberg responses on such a change.
I also like to address that power user not really into automatic user experience sharing and therefor this this group get underestimated in user stats.
|
|
||
Comment 6•5 years ago
|
||
It has been reported multiple times, thanks.
|
||
Comment 7•5 years ago
|
||
We've been through this already with you in bug 1703504. You really can't keep creating the same bug, your account may end up disabled if you continue in this vein.
As an developer i cannot accept such an important workflow issue. If the ones who care -we on this platform- want discuss why it needs to be changed and every appearance of this issue is silenced, making an new bug/enhancement report is the only option. The fact this is an "community based" software development, dozens of people like me who specially for this issue make the effort to get to this platform to get listen to and all the voting for bug 1621570 , must ring some alarm bells. Doesn't it? We are only the top of the ice-berg that's indicating the ClickSelectsAll behavior is an serious issue and people hate it.
I will and keep making reports till Firefox, the browser i use from the beginning, works like i want. Until last year i was able to configure it like i want. Now developer or stakeholders (As Marco described) like to work towards an browser for common users who just use it as it occurs. I, and many developer with me will not accept this strategy. Never!
Description
•