We better document this weird behavior... out of curiosity, does it work the same if you set opacity to any other value (between 0 and 99)?
1 Like
Yes, it works with any value between 0-99
Don't know what the problem with 100. I didn't want the background to be transparent that's why I set it to 99.
Well, I can't be sure, but CSS uses so-called "stacking contexts" to decide what should be rendered first. Enabling opacity (setting it to a value between 0 and 100%) will make the target element stack, which effectively changes how it's rendered into the screen.
Now, why this happens to help in this case... in theory borders nor backgrounds should be affected by this. But it this immediately came to mind when you said that setting opacity to 99% worked. I'm guessing things work a little differently with XFCE?
Then everyone should be affected. But I could not replicate it.
Good point 
I have to respect those who create themes even more as it's incredibly confusing to keep track of all the little things like this.
I should have added exact details how it worked on my side.
Adding the following lines to gtk.css and then changing the opacity value from whiskermenu settings.
#whiskermenu-window frame>border {
border: none;
}
-x-
Or xfce render things differently on different hardware specifications and display configuration?
(I don't know how xfce works I just guessed this as there was no such issue when Aravision tried it)
I actually think this is more likely a compositing issue.
Looking back, I recall we did ask whether the compositor was enabled, but did not actively check the settings to see if effects like borders and shadows are applied when windows are fully opaque.