Stop overlapping other toolbars with the focused urlbar
Categories
(Firefox :: Address Bar, defect, P2)
Tracking
()
Tracking | Status | |
---|---|---|
firefox-esr68 | --- | unaffected |
firefox71 | --- | disabled |
firefox72 | --- | disabled |
firefox73 | --- | disabled |
firefox74 | --- | verified |
People
(Reporter: dao, Assigned: dao)
References
(Blocks 1 open bug)
Details
Attachments
(1 file)
From https://mozilla.invisionapp.com/share/DNSDVW5E8QK#/screens/367251846_Photon_Design_Update:
"When the quantumbar is automatically focused (startup, new tab, clicking home, new window) and the Bookmarks Toolbar is displayed, the toolbar will get a 10px top margin so bookmarks clear the bottom. If the quantumbar loses focus, the toolbar's margin will animate away along with the quantumbar to its unfocused state."
Updated•6 years ago
|
Updated•6 years ago
|
Assignee | ||
Updated•5 years ago
|
Updated•5 years ago
|
Assignee | ||
Comment 1•5 years ago
|
||
I'm not quite convinced of the proposed UX here e.g. as it implies shifting the whole content area. I propose we just don't expand the urlbar at all when the bookmarks toolbar is present. mconnor is going to discuss this with verdi.
Comment 2•5 years ago
|
||
Mike and I discussed this today and agreed that we should go ahead and implement it.
Comment 4•5 years ago
|
||
(In reply to Verdi [:verdi] NI or PM me from comment #2)
Mike and I discussed this today and agreed that we should go ahead and implement it.
is "it" mean "don't expand the urlbar at all when the bookmarks toolbar is present" in comment #1 ?
if so, can we change the bug summary for clarity?
Comment 5•5 years ago
|
||
(In reply to Tooru Fujisawa [:arai] from comment #4)
(In reply to Verdi [:verdi] NI or PM me from comment #2)
Mike and I discussed this today and agreed that we should go ahead and implement it.
is "it" mean "don't expand the urlbar at all when the bookmarks toolbar is present" in comment #1 ?
if so, can we change the bug summary for clarity?
No it means we're going to do what the bug title says - shift the bookmarks toolbar downwards when the urlbar is focused in new tabs.
Comment 6•5 years ago
|
||
so, this bug covers the case for new tabs (that shows about:newtab), right?
should we open another bug for non-new tabs? or does bug 1585958 cover the case?
Comment 7•5 years ago
|
||
(In reply to Tooru Fujisawa [:arai] from comment #6)
so, this bug covers the case for new tabs (that shows about:newtab), right?
Yep.
should we open another bug for non-new tabs? or does bug 1585958 cover the case?
No. On non-new tabs we don't autofocus the address bar so it doesn't cover anything until you interact with it.
Comment 8•5 years ago
|
||
The fact that it changes the viewport of the browser is going to be pretty annoying / have side effects like content jumping around, which is not great.
Comment 9•5 years ago
|
||
I must note it's only on "(startup, new tab, clicking home, new window)", on normal focusing it won't do it.
Assignee | ||
Comment 10•5 years ago
|
||
How are we supposed to handle the whole content area shifting as the urlbar loses focus the moment the user interacts with the new tab page?
Assignee | ||
Updated•5 years ago
|
Comment 11•5 years ago
|
||
when (in which timing) does the bookmark bar shifts and unshifts ?
what happens when user starts interacting with bookmark bar (like, opening bookmark folder, drag and drop item) while urlbar is expanded?
Comment 12•5 years ago
|
||
The fact that it changes the viewport of the browser is going to be pretty annoying / have side effects like content jumping around, which is not great.
Also, in general, seems to conflict with the idea of compact density. Maybe disable this behavior when compact density is set?
Comment 13•5 years ago
|
||
What about extensions that change the new tab page? There is quite a few of them that use the top-most part of the page, or can be configured to do so.
I have a custom made new tab page that uses webextension API to create a bookmarks bar, and there is at least a few extensions on AMO that have the same functionality.
Maybe decrease the bottom padding of the megabar when there is a non-default new tab page so it won't cover content?
Assignee | ||
Updated•5 years ago
|
Comment 14•5 years ago
|
||
(In reply to Dão Gottwald [::dao] from comment #10)
How are we supposed to handle the whole content area shifting as the urlbar loses focus the moment the user interacts with the new tab page?
I'm not quite sure what you are asking. Maybe we can delay moving the content until mouseup so that targets don't move under the pointer and maybe we can skip moving the content if another url has been requested.
Comment 15•5 years ago
|
||
(In reply to Verdi [:verdi] NI or PM me from comment #14)
(In reply to Dão Gottwald [::dao] from comment #10)
How are we supposed to handle the whole content area shifting as the urlbar loses focus the moment the user interacts with the new tab page?
I'm not quite sure what you are asking. Maybe we can delay moving the content until mouseup so that targets don't move under the pointer and maybe we can skip moving the content if another url has been requested.
about:newtab contains things that require multiple click (I mean, not something that triggers pageload by one click) to interact.
example case with Top Sites menu:
- click "..." button next to "Top Sites"
- a menu is opened under the button
- click a menu item there, or just click elsewhere to close the menu
another case in search field:
- click search field
- secondary click there to open context menu
- a context menu is opened next to the cursor
- click "Paste"
- click arrow button to search the pasted text
in both case, if a content slides up in any timing, that will be annoying.
if something else than about:newtab is opened there by extension, similar case will happen there also.
also, the same thing happens when user starts interacting with bookmark toolbar items.
Comment 16•5 years ago
|
||
Why not change the behavior to only expand the megabar once the user starts typing (or results are displaying via clicking the drop-down arrow)? It seems like that would address a lot of the usability/UI concerns with the current implementation/design without making the UI feel even more janky.
Assignee | ||
Updated•5 years ago
|
Assignee | ||
Updated•5 years ago
|
Assignee | ||
Comment 17•5 years ago
|
||
Comment 19•5 years ago
|
||
Comment 20•5 years ago
|
||
bugherder |
Comment 21•5 years ago
|
||
I can confirm this fix on the latest nightly(Fx 74.0a1: 2020-02-04), I verified on Windows 10 x64, Ubuntu 18.04 and macOS 10.15.
Updating the flags accordingly.
Description
•