I'm happy you guys announced it and posted visual proof of why you decided to defederate from them.

Trasparence in the management will shine a bright way ahead!

I don't find it useful I guess?

On computers where I've got high specs, if I want a quick look on a tab it's faster to just switch to that tab rather than waiting for me to hover on the tab and get a preview of it, so I guess I could keep it there, but I feel like it distracts me on the rare occasion I have to close a tab clicking on the X with the mouse (I rarely do it, usually I'm a kb shortcut guy)

On computers where I got low specs, I feel like the tab hover preview is just something that doesn't actually give me any benefits and instead just slows more a modest specs system when I move the mouse on the tabs for whatever reasons.

I'm glad FF is introducing more things of course, I can see the appeal for the general public, but it's not for me I guess?

As a 6 years Infinity user, thank you for starting Beyond! Can't wait for it to grow!

Looks hella cool to me! Nice one, thanks!

Nice guide!

Everything is on point, I just wonder if the "making uc.css red in toolbox" part is still useful nowdays tho?

I remember I had this as well, but since browser toolbox started supporting search I didn't feel it useful anymore, but that could be just me :D

EDIT: I just forgot to activate the browser toolbox on this new pc. My bad.

Thanks!

Thanks! This works as well!

Really appreciated!

Sadly it doesn’t seem to work in my case (?)

Thanks! I opened my FF.exe directory location, found the omni.ja file, but I'm having trouble opening it, any idea?

Thanks! That site seems veeeeery useful!

Oh I see, a bug was affecting it, curious ahah! Thanks for pointing it out and thanks for the quick fix solution as well :D

Yeah, same stuff happens to me. I don't understand if this is working as intended or if something is off...

Oh, cool! Thanks! :D

Oh, I see. I think that's probably it!

So the only way to have context menus that can be styled with css is disabling widget.macos.native-context-menus, will try this thanks!

Oh, you're right on the border image, thanks!

As for the other separator, I totally thought it was native, but after reading your comment I started searching in my css files and I found what was causing the green circled issue. Apparently it's this part of the code here:

/* Add somewhat hacky separator to zoom controls so it looks consistent */
#appMenu-protonMainView > .panel-subview-body::after,
#appMenu-mainView > .panel-subview-body::after {
  content: "";
  display: flex;
  border-bottom: 1px solid var(--panel-separator-color);
  margin: var(--panel-separator-margin);
}

which is a part of one of your styles . I'm pretty sure I had this for well over a year since I basically considered it native. When I removed it while keeping the rest, it seems like it's working just fine anyway. Thanks for the help!

Unrelated side question that I don't think it's worth enough to open a thread on different spaces: to test the code I used both Windows 11 and MacOS Tahoe, I noticed that the quit option is missing from the macOS arrowPanel compared to the Windows one. Here's the comparison (mac on the left, w11 on the right) I probably think this is normal as I noticed this in a native, non modded profile (in macOS the about firefox in "Help" section of the arrowPanel is missing as well compared to the Windows one so it wouldn't be strange if quit one is missing as well) but do you happen to know if what I just said is actually right? It's not really important, more like a curiosity lol

yes i'm 100% sure, I get it from the official firefox website on macOS. The same difference appear in troubleshoot mode (just without the icons)

can it be seen now?

that is a script yeah, but it shouldn't impact this. The icons are added with css yeah, mostly by your snippet. The screen are exactly the same without icon and restart button in the troubleshoot mode, I'd retake then but currently don't have access to the w11 desktop.

It's getting interested so I'll tru to ask around on firefox communities and report it back here for knowledge purpose