Why isn't bleeding corner fix mod just enabled by default?

[gordonn]

Its only one line of CSS:
.browserContainer { clip-path: inset(0 round var(--zen-native-inner-radius)); }
So why isn't it the default setting? I heard somewhere that it has to do with performance but that seems a little preposterous. I added this line to my own userChrome.css for now to test how performance is and will have a better idea soon.

[Anthonyy232]

https://stackoverflow.com/questions/52126678/is-there-a-reason-clip-path-a-div-with-an-image-inside-slows-performance-in-chro

Also
#6302 (comment)

TLDR: eats GPU performance. Many folks do not have a capable GPU.

[gordonn]

@Anthonyy232 That's interesting. Don't see much performance drops on my desktop. Maybe its more prominent on lower performance systems. Is there really no work around for the bleeding corners?

[gordonn]

@Anthonyy232 I have this line of CSS in userChrome.css and its working fine on my laptop. There may be some performance decreases but it isn't evident with current use.