I get it, I’m an end user too. But I also have been working with computers long enough to know how forks work. When you use a fork, this happens.
So again, you can’t force something just because as an end user you don’t like it. We don’t like it either, and I bet the devs don’t either. But again it does take time.
I’m gonna link you to one of my own complaints and lead by example here: Broken 30-bit color when ACM enabled with scRGB color space
See how the issue not only went unsolved and ignored? Check my edits and my own replies to myself, I ended up realizing it was a Chromium regression. So know what I did? Filed a ticket with Chromium. But guess what, it went nowhere there as well.
Do I expect Brave to fix it? Well, no. They specialize in privacy, security, that stuff. Half the devs probably don’t even have a setup like mine to have a 30-bit color depth to use the color space I use, so it falls in the cracks.
Point is, I found where the issue was, and don’t blame nor expect Brave to fix it, because I know Brave is a fork of Chromium.
Do realize, it’s Chromium’s developers that leave users waiting months to years. I know, I’ve dealt with them in the past.