I'd like to propose a suggestion on the contextual bar. Though it does add some extra buttons either in the URL or tab bars. It could be a button in the URL or tab bar. Though rather than that, I'd say presenting the contextual bar as a little stub, from the top of whichever bar is in heirarchy, (unlike currently where it is showed under the URL bar) like a floating pinned triangle icon (or any) that I could click on and it could show these contextual icons.
This bar, as I can see is already scrollable as well which makes it perfect too present it as a separate dynamically thing. Basically the idea is not to have this bar constantly pinned all the time. And when we hide the URL + tab bar and it presents itself in a floating icon. It could show two floating icons comosctly placed so I could access the contextual bar in a very quick manner.
On that note, when the tab+url bar is hidden for a tab I noticed that it acts on a per tab basis. Which is, probably one of those things that potentially causes the issue experienced in this one issue by me and @Flanr4 #502 (comment) here.
Wouldn't it be much better to actually hide the tab bar for all tabs. I can see why some may like it to be hidden in one tab and visible in the others. So I'd like to propose to convert the floating button part to act in two modes. Long pressing or flicking up from the floating icon actually brings the tab + url bar permanently. Otherwise just clicking on it once shows the entire bar in a floating mode which hides itself once a user clicks out of it. With the 2nd floating icon giving users the contextual menu, they subsequently hide the bars and still have the ability to do most of the functions. And when they switch to other tabs, the bars would remain in a floating State, either collapsed back to the floating button or remain as the tab unless the user click outside of the bar. Which any interaction on the page would collapse it back. That would prevent the flickering issues that come due to tabs which have the bars collapsed to a floating icon vs tabs which don't since at the moment it works on a per tab basis and not globally.
I'd like to propose a suggestion on the contextual bar. Though it does add some extra buttons either in the URL or tab bars. It could be a button in the URL or tab bar. Though rather than that, I'd say presenting the contextual bar as a little stub, from the top of whichever bar is in heirarchy, (unlike currently where it is showed under the URL bar) like a floating pinned triangle icon (or any) that I could click on and it could show these contextual icons.
This bar, as I can see is already scrollable as well which makes it perfect too present it as a separate dynamically thing. Basically the idea is not to have this bar constantly pinned all the time. And when we hide the URL + tab bar and it presents itself in a floating icon. It could show two floating icons comosctly placed so I could access the contextual bar in a very quick manner.
On that note, when the tab+url bar is hidden for a tab I noticed that it acts on a per tab basis. Which is, probably one of those things that potentially causes the issue experienced in this one issue by me and @Flanr4 #502 (comment) here.
Wouldn't it be much better to actually hide the tab bar for all tabs. I can see why some may like it to be hidden in one tab and visible in the others. So I'd like to propose to convert the floating button part to act in two modes. Long pressing or flicking up from the floating icon actually brings the tab + url bar permanently. Otherwise just clicking on it once shows the entire bar in a floating mode which hides itself once a user clicks out of it. With the 2nd floating icon giving users the contextual menu, they subsequently hide the bars and still have the ability to do most of the functions. And when they switch to other tabs, the bars would remain in a floating State, either collapsed back to the floating button or remain as the tab unless the user click outside of the bar. Which any interaction on the page would collapse it back. That would prevent the flickering issues that come due to tabs which have the bars collapsed to a floating icon vs tabs which don't since at the moment it works on a per tab basis and not globally.