Taher A Alkhateeb

I've upgraded to 6.6.1 and the issue seems to be still not resolved.

I also confirm the bug, building from source with `cargo +stable build --release --all-features` it smells like a relative file location issue, I'll try to investigate.

I think this is already [fixed](https://github.com/moqui/mantle-usl/commit/75ae93ed91853edadb8760af09fd3667ca7d2f26) and so it might be better to close this ticket. Although this caused another problem which we'll report in another ticket

I believe this is still an issue, and I tried all the solutions above and none had worked. On macos arm64 and the sharp package refuses to install on a...

OK I think I solved by simply excluding sharp and nothing else. This is my exact code to solve in package.json: ``` "pnpm": { "onlyBuiltDependencies": [ "sharp" ] } ```...

@pippinmole I tried that command and it generated a whole bunch of useless stuff, made duplicate entries and it was a mess. I believe the above snippet is minimal and...

I also confirm this bug. Arch linux on i3wm 

@harridu I think the problem actually originates in Chromium and not necessarily in Brave. It seems to be just more visible in Brave. When I open the menu in dark...

@harridu Fixing the border might be fixing a mistake with another mistake. The root cause is shadow rendering and I would imagine that's what the brave team should attend to....

@egbastos666 I would suggest that introducing a compositor is a discussion in Chromium. Brave as a derivative product is different flavor of Chromium but it _is_ Chromium. I'm also not...