Awsomebar is broken
Categories
(Firefox :: Address Bar, defect)
Tracking
()
People
(Reporter: ujze, Unassigned)
Details
User Agent: Mozilla/5.0 (Windows NT 6.1; Win64; x64; rv:68.0) Gecko/20100101 Firefox/68.0
Steps to reproduce:
1.Open browser.
2. Clkick adress bar. The urlbar when clicked gets larger and covers the bookmarks bar.
3. After click when no longer active, is still larger and still covers the bookmarks bar. Readability of bookmarks tab is screwed.
4. The Esc-key does not work to hide focused urlbar.
5. When focus on the address field now by clicking somewhere in it, a list of most popular bookmarks drops down.
6. History drop down no longer wisible.
Actual results:
I don't know. Everything mesed up after update to version 75
Expected results:
Address should be static. Not bigger than his container in the theme. Should work and look like in version 74.
|
||
Comment 1•5 years ago
|
||
I believe there's already a bug on file for each of the points, but leaving to component owners to confirm.
|
||
Comment 2•5 years ago
|
||
I'll dupe to the bookmarks toolbar bug, since all the rest has been largely discussed elsewhere already and it's by design anyway.
Is there really no plan to reconsider the design itself? Almost every day, someone files a bug which basically evaluates to "the design itself is broken".
|
|
||
Comment 4•5 years ago
|
||
We are already considering all the incoming feedback, we don't need a "design is broken" bug (it would indeed be considered invalid since there are subjective matters involved and actual issues are actively being tracked already).
(In reply to Marco Bonardo [:mak] from comment #4)
We are already considering all the incoming feedback
Thanks, that's good to know!
(In reply to Marco Bonardo [:mak] from comment #4)
there are subjective matters involved
Where do you draw the line? If there are, I don't know, 5 people in the UX team saying the address bar should enlarge and 25 people filing bugs saying no, it looks ugly that way...
|
|
||
Comment 6•5 years ago
•
|
||
We have to ponder feedback, product requirements and expertize on that matter, along with proper measurements on the field. Thus answering your question is not trivial, there's no magic wand. Usually the questions are "do we expect this to help most of our users? what can we do to enlarge that group? how can we handle the most compelling remaining problems?". The solution is rarely "just disable it", because doing a change starts first of all from a need, and going back you'd just restore that need. The UX team listens to feedback and runs studies with real randomized users to understand problems, it's not just matter of designing something on paper.
(In reply to Marco Bonardo [:mak] from comment #6)
Usually the questions are "do we expect this to help most of our users? what can we do to enlarge that group? how can we handle the most compelling remaining problems?". ...doing a change starts first of all from a need... The UX team listens to feedback and runs studies with real randomized users to understand problems, it's not just matter of designing something on paper.
This is comforting and I just wish that it was somehow communicated better instead of in the comments of an obscure bug. I and many more people updated to 75, saw the enlarged address bar in surprise, thought "what is this uglyness", maybe read the release notes saying that it is "focused, clean, optimized, improved", and the idea we got was that somebody with a bad sense of design is making arbitrary decisions. That's when we flocked to Reddit and Bugzilla where we got many responses saying WONTFIX, or just a terse "this is by design" which disheartened us even further. (even if true, bad communication?) It might be that the release notes for such a visible UI change should include a link saying "here's where you can provide feedback" -- I don't know, I'm not an expert at communication, but the sieges of Bugzilla that routinely happen with some of those changes (I recall the old extension system deprecation, or an earlier search bar redesign where the same thing happened) are maybe indications that people are actively looking for, and not finding, the proper ways to voice feedback.
Which is actually a positive thing IMO. I don't use Chrome but if I did, I wouldn't dream I have any say in what Chrome devs do. Firefox on the other hand still feels like "my" browser, the browser that serves me instead of some corporate interests. There was this survey a while ago that asked us Firefox users how we feel about Firefox and that was one of the possible answers. Maybe, just maybe, if the feedback is loud enough, the megabar incident could be retrospectively evaluated in that context: how likely did this change convince users that no, this browser is not really yours.
But at least please run measurements on how many people disabled the new address bar with about:config or userchrome.css.
Description
•