hansman 6mo ago • 100%
hansman 6mo ago • 100%
Frankly, the community was less willing to move to another platform than I had hoped, but perhaps now is a good chance to try again :)
Let's hope so; and thanks for chiming in.
But more importantly - how do you like your new nick: MOG? ;P It sure is easier to type.
hansman 6mo ago • 100%
[Repost]The FirefoxCSS archive really should be maintained; it is a unique source of info even though many codes are partially outdated.
However, for a long time, the discussions on that sub have been dominated by spammers requesting support for extensions, or showing off useless personal setups.
Then there are the many posters who will not engage in a discussion on css code, simply expecting a quick fix regardless of the complexity of the issue; not to mention the many efforts by contributers which go unanswered.
Since hardly anyone seems to be unduly bothered by the possible demise of that sub - including our very own MrOtherGuy ;) - I assume that there is little if any interest in discussing the finer points of Firefox specific CSS coding.
hansman 6mo ago • 100%
Thanks again; I kinda managed to target the highlighters' css with force by js, but it's getting too much trouble at this point.
hansman 6mo ago • 100%
Thanks for the reply, seems like the same issue indeed. Do you happen to know how to target that tooltip, or know it's selector?
This one has been driving me crazy for ages... When I use the Browser Toolbox - with the option `Disable popup auto-hide`being checked - and I hover over or select an element in the inspector , the info panels/tooltips that are usually displayed above and/or in front of the targeted/selected elements are covered by the open popups. Also, the selected UI popup parts are not highlighted as they would be for other bits, there's only that dotted grid visible - again partially hidden - that gives you a general idea of what you are looking at. This is on MacOs/Fx 115esr; I understand the issue is the same on Windows. I've tried lots of css and javascript codes to find a way to target that thing, but to no avail. The Fx popups in general have a silly high z-index, so that might be part of the issue; I'm wondering if there's any way to fix that. Screenshot below. ![Screenshot](https://imgur.com/a/kJnErj1)
hansman 6mo ago • 100%
I hope it's just a glitch, or the boss mon went too far into his jazz cabbage.
hansman 8mo ago • 100%
Thanks mate, great explanation.
hansman 8mo ago • 100%
Glad it's working!
As for discussions on it, I've linked to a couple in my first reply, and there's one in a German forum.
Credit for the solution goes to this poster; the related Fx code might be this one.
hansman 8mo ago • 100%
Well, have you tried the code?
It might interfere with the css style, which is creating its own navbar shadow, but that might be (partially?) overriden by current Fx versions anyways. The issue has been discussed in a couple of other forums, seems like the code for that shadow has changed recently.
Again, maybe give this a shot, which has worked for some other users; to be safe put it at the bottom of your userChrome.css, shouldn't matter though:
#nav-bar:-moz-lwtheme {
box-shadow: none !important;
}
hansman 8mo ago • 100%
If it's the box-shadow causing the issue, in my testing it will only be visible in (most?) 3rd party themes, I couldn't see it in the official Fx and system(Mac) themes either.
On the other hand, that shadow should then go all across the bar, not just show under the selected tab. Unless the chosen theme or his custom css moved things around a bit.
hansman 9mo ago • 0%
I'm not quite sure what the issue might be, chances are this fedia thing isn't showing me any code or screenshots you might have added to your post.
Just a very wild guess, could it be the nav-bar shadow, which could previously be removed with something like that:
#nav-bar:-moz-lwtheme {
box-shadow: none !important;
}
Maybe check if there is a that shadow listed in the browser tools, and if so how it is applied in FX123; also if the issue occurs with every theme, or just the ones that are not native Fx or system themes.
hansman 11mo ago • 100%
But the hamburger button doesn't usually do that.
Unless you are using weird custom css code.
I've been playing around with a little CSS code for curved tabs recently, inspired by this [style](https://github.com/MrOtherGuy/firefox-csshacks/blob/master/chrome/curved_tabs.css) by MrOtherGuy. It seems to work reasonbly well so far - still a work in progress - but one issue I just can't figure out - when the tabs are overflowing, the additional bottom corners I created for the outer tabs are cut off, unless they are the very first or last tab (which are taken care of). I've tried every selector and element in this area, to change the cutoff/clipping points of these outer visible tabs in overflow, or the width/padding etc. of the scrollbox "window", but to no avail. Any ideas would be much appreciated. The code can be found [here](https://pastebin.com/JLxSXsqW), a screenshot is attached showing the issue. I hope the .svg code in the CSS file works, if not this is it: ``` <svg xmlns="http://www.w3.org/2000/svg" width="128" height="128" viewBox="0 0 32 32"> <path d="M0 33 L3 32.5 A16 16 0 0 0 15.5 16 L 16 16 L 16 33 Z" fill="context-fill"/> <path d="M3 32.5 A16 16 0 0 0 15.5 16" fill="rgba(155,122,0,0)" stroke="context-stroke" stroke-width="1px"/> <path d="M0 16 L16 16 A15.5 15.5 0 0 1 32 0 L 32 0 L 32 16 Z" fill="rgba(155,122,0,0)"/> <path d="M15.5 16 A18.5 18 0 0 1 35.5 -0.5" fill="transparent" stroke="context-stroke" stroke-width="1" /> </svg> ```
hansman 1y ago • 100%
That worked, thanks.
Yeah, those new message boards can be a bit finicky. ;)
Glad you found a solution.
hansman 1y ago • 100%
Well, worth a try.
As for the screenshot, I can't see it; is there one?