Re:Google has removed the option to disable autoplay from Mo...
by javieranton on Sunday September 20, 2020 @07:47AM
(#24533424)
That may be obvious to you. I had never filled a Chromium bug before and didn't know whether they were going to even have a look at it. Lookin g at the bug link you can see how widespread the damage was because of the recent update. It affected lots of people and its effects were that fps were down to 5 from 60 so yeah, pretty bad. Google doesn't really give a damn in certain areas (i.e. API) where their support is non existent unless you are sone type of VIP. So apologies for coming here with this, I guess I didnt know as much about Chromium bugs process as you do
Asking on HN for a random chrome engineer using a fresh throwaway (created for this specific post) to look at your 11 hour old low priority performance bug for a specific piece of hardware seems misguided. There are hundreds of engineers working on Chrome -- it is extremely unlikely this person is the right SME for this bug, and even if they were, how could they possibly do anything to your bug internally without revealing their identity?