-
Notifications
You must be signed in to change notification settings - Fork 1.3k
Visible URL width #3727
Comments
The usages of blank space between url bar, tab button, menu dots is excessive! 'https://' or 'http://' should be omitted from showing in url bar bcz these are redundant whenever a secure buttons is visible or there may be a preference for showing the url prefix. |
We try to respect the 48x48dp touch target size to make it easier to navigate around.
Yes, we can hide the protocol (http://, https://) to gain some space (cc @vesta0 does this sound ok to you?) |
Fennec uses less blank space between tab button and 3-dot menu. Do we need all that space in order to have a usable touch target @topotropic ?
Yes or we can do what Fennec does = keep the http:// and https:// but keep it out of the visible URL area @topotropic |
@vesta0 yes, we need all that space to have usable touch targets, we might be able to make the touch target a tiny bit smaller but that won't do much to increase the visible URL part What do you mean with "keep it out of the visible URL area"? |
That is referring to the fact that Fennec tries to scroll the URL such that the end of the host part aligns with the right edge of the URL bar, which means that for URLs where the host part doesn't fit within the width of the URL bar, it's the start of the URL (including the protocol) that gets pushed off the screen. |
Related #4560 |
Posted #5302 |
... and we don't even support webextension page actions yet, which would require space in the URL bar, too. |
We addressed this in #7077 7077 |
On my phone, in Fenix there are around 380 px (190 dp) available for displaying the URL itself, whereas in Fennec this value is (depending how much of the fade out you count) approximately 460 - 470 px (230 - 235 dp). Fenix seems to partially compensate by using a smaller font size, but for the same amount of buttons in the URL bar, I can still see more of the URL in Fennec.
Fennec:
Fenix:
┆Issue is synchronized with this Jira Task
The text was updated successfully, but these errors were encountered: