Inconsistent padding logic for left and right window control buttons

[MaxHasBeenUsed]

shimmer/userChrome.css

Lines 1245 to 1259 in 5c4c286

	.titlebar-close {
	/* background: hsl(355, 86%, 49%) url(chrome://browser/skin/window-controls/close.svg) no-repeat center !important; */
	&:hover > image {
	background: #fc5753 !important;
	}
	padding-right: calc(var(--shimmer-winctr-gap) + var(--shimmer-winctr-margin)) !important;
	padding-left: var(--shimmer-winctr-gap) !important;
	}
	.titlebar-min {
	&:hover > image {
	background: #fdbc40 !important;
	}
	padding-left: calc(var(--shimmer-winctr-gap) + var(--shimmer-winctr-margin)) !important;
	padding-right: var(--shimmer-winctr-gap) !important;
	}

Here the padding is hardcoded so that --shimmer-winctr-margin can only be on the right side of max button, or left side of the min button. But when the close button is on the most left side, like:

Adjusting --shimmer-winctr-margin no longer does what it supposed to do.

Probably related to #3

[MaxHasBeenUsed]

For anyone having this issue, quickest fix is:

 .titlebar-close { 
 	...
 	padding-left: calc(var(--shimmer-winctr-gap) + var(--shimmer-winctr-margin)) !important; 
 	padding-right: var(--shimmer-winctr-gap) !important; 
 } 
 .titlebar-min { 
 	...
 	padding-right: calc(var(--shimmer-winctr-gap) + var(--shimmer-winctr-margin)) !important; 
 	padding-left: var(--shimmer-winctr-gap) !important; 
 } 

The reason I didn't open a pr is... Right now reversing the buttons didn't flip them, and I'm not sure if this is an intended behavior.

By flip I meant something like:

with shimmer.reverse-winctr-buttons-side == False, buttons min max close on the right;

and with shimmer.reverse-winctr-buttons-side == True, buttons close max min on the left.

[nuclearcodecat]

flipping was never implemented, the config option just moves the buttonbox to the left side iirc.
you can open the pr, things can be changed in it later :3
i'm unsure if i can properly test this, as on hyprland only the close button is spawned, although the rest might just be hidden. we'll see