-
-
Notifications
You must be signed in to change notification settings - Fork 190
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Autohide both toolbar and navbar results in not being able to click the top area completely without toolbar interference #995
Comments
This is really annoying... |
@black7375 some information: the video is from the userjs 8.6.3 which I applied on Firefox nightly version mentioned which I use on my Linux. But I'm not facing that issue that much on my floorp browser with same lepton photon style which floorp has inbuilt into their browser. Point is that the version of lepton photon userjs floorp is using as of writing (11.19 probably) do not have that bug and I'm able to click that area manageable-y without interference. If you use Firefox in full screen mode with all these same settings (autohide and lepton photon userjs) the interference completely goes away and the toolbar doesn't reappear that quickly (I think this specific part can already be dealt by increasing that 0.x second "delay" of toolbar appearance). |
@Rtizer-9 See if these rules fix your problem @-moz-document url(chrome://browser/content/browser.xhtml){
@media (-moz-bool-pref: "userChrome.autohide.tabbar") and (-moz-bool-pref: "userChrome.autohide.navbar") and (-moz-bool-pref: "userChrome.autohide.navbar") and (not (-moz-bool-pref: "userChrome.tabbar.one_liner")),
(-moz-bool-pref: "userChrome.autohide.tabbar") and (-moz-bool-pref: "userChrome.tabbar.one_liner") and (-moz-bool-pref: "userChrome.autohide.navbar") and (not (-moz-bool-pref: "userChrome.tabbar.one_liner")),
(-moz-bool-pref: "userChrome.autohide.navbar") and (-moz-bool-pref: "userChrome.autohide.navbar") and (-moz-bool-pref: "userChrome.autohide.navbar") and (not (-moz-bool-pref: "userChrome.tabbar.one_liner")),
(-moz-bool-pref: "userChrome.autohide.navbar") and (-moz-bool-pref: "userChrome.tabbar.one_liner") and (-moz-bool-pref: "userChrome.autohide.navbar") and (not (-moz-bool-pref: "userChrome.tabbar.one_liner")) {
/* fix click through onto window frame when bar's hiding */
#mainPopupSet:not(:hover)~#navigator-toolbox:not(:hover, :focus-within) #nav-bar:not([customizing]) {
-moz-window-dragging: no-drag;
}
/* fix url bar un-hide before reach */
#navigator-toolbox:not(:hover, :focus-within) #nav-bar:not([customizing]) #urlbar {
pointer-events: none;
}
}
/* fix nv bar hide when hover on tab bar */
toolbox#navigator-toolbox[id],
body,
:not(body) {
--browser-stack-z-index-devtools-splitter: 2;
--browser-stack-z-index-dialog-stack: 3;
--browser-stack-z-index-rdm-toolbar: 4;
--browser-area-z-index-toolbox: 1;
--browser-area-z-index-sidebar: 2;
--browser-area-z-index-tabbox: 3;
--browser-area-z-index-sidebar-splitter: 4;
--browser-area-z-index-toolbox-while-animating: 5;
}
#navigator-toolbox:is(:hover, :focus-within)~#browser {
z-index: 0;
}
} All the same to #1062 but without bar transparent and context menu un-hide part. |
@117649 I don't have any issues with auto-hiding as I've already mentioned to you in 1028 and if this alternate method of yours is working for you, why is 1028 still open? You're the one having issues right? This issue was opened in Sept 30 and ui-fix last update was on Nov 30 so I don't get it why you're commenting here when 1028 is already open. And this bits of patches you're suggesting aren't going to cover all the cases and the extra lines are there for a reason so as you mentioned in 1028 that the 2 lines that you copied from the css I suggested is enough isn't going to be indeed enough and cover all the cases. What the issue is about is that ui-fix repo code needs to be updated officially so that we don't need other css. |
Issues in a repo is of the repo and for the repo. As long as the issue is not address by repo usually in the form of a commit of fix the issue won't be closed. And it is of course OK to commenting here no matter you close it or not as long as it is related to the issue. And my rules here and there are both indeed enough to cover all the cases they were supposed to according to the issue they were posted. For the very reason that they were tested to fix the very core of the problem. If you don't have minimum understanding of the css or anything mentioned above don't bother making any issue any more. You're just causing more issues. |
What does this even mean?
Yes exactly that's why this issue was open to let the developer know that the problem is still present; I closed it now because with 1028 open this isn't relevant anymore. I literally told you in 1028 that I've found the solution and I'm not facing the issue anymore so why are you acting like as if you suggested the solution that conversation never took place in 1028.
Yes here comes the true colors, basically that's what it's all about. You just don't want to acknowledge somebody can have better CSS than yours. I suggested you the other CSS, on a issue "you" created, for which you didn't say a single thanks and instead tried to patronize other user ironically when you found your "solution" from the code other user suggested to you. And then you went on to edit that comment 3 times when nobody gave you any attention by commenting. If you already know so much of CSS why exactly did you open 1028? It's because you couldn't find the solution. We both have created one issue each so what is this about creating more issues. Communities are for helping and sharing and not trying to prove who knows better and that's the only reason I brought that other css to your attention to help you because I was having same issue but seems like your ego got hurt. Grow up, this know-it-all attitude isn't gonna help you. |
Too long and every bit worthless shit. Here is not your usual SNS trolling ground. NO kindness will be grant automatically. Effect is only standard. |
Describe the bug
Choosing autohide option for both toolbar and navbar results in not being able to click anything on top area completely without toolbar reappearing inbetween.
You can't click those things without the toobar reappearing inbetween resulting in clicking on toolbar instead of those things you actually want to click.
Expected behavior
You should be able to click those things without the toolbar reappearing inbetween.
Screenshots
338680350-b993d4f2-2244-4d0c-a6f1-e0d4b8ed45b9.mp4
OS
Linux
OS - Others
No response
Firefox Version
132.0a1 (2024-09-29) (64-bit)
Distribution
Theme
Theme - More Info
Matte Black (Red)
https://addons.mozilla.org/en-US/firefox/addon/matte-black-red/
user.js
setupuser.js
setupThe text was updated successfully, but these errors were encountered: