> and I'd love to to hunt this down and fix it but have no clue where to start. I guess the first step would be to consistently reproduce the bug...
I am not familiar with Chromium at all, and I also don't run Linux on the desktop as I'm guessing from your video you do (?) so take this with a grain of salt...
I would start looking at the focus and key event handlers. e.g. maybe log the contents of pressed_keys and/or step thru the code from the beginning of the focus handler. It looks like this might be the place:
Even if you can't repro it, you may be able to figure out the issue by just reading thru that code with some theories in mind. e.g. Since pressing another key seems to fix it, maybe look at what the code is doing there... my guess is the release event fixes whatever corrupted state it is in upon focus.
The Apple Watch Noise app measures loud noises. The Health app on iOS has a section called Environmental Sound Levels that shows the measurements over time on a chart. This of course doesn't help if you can also hear the noises, but it sounds like that is not the case?
We can't hear the noises. Something like the Apple Watch noise monitoring would be great as we could say "see, the decibels haven't gone above x in the last week" but as far as I can see it doesn't give you this info over time
The measurements taken by the watch can be viewed over time in the Health app on iOS. Try image searching for "Environmental Sound Levels" "iOS" "Health" to get an idea of how it looks. e.g. here is a screenshot: https://www.idropnews.com/wp-content/uploads/2023/04/Apple-H...
Try Decibel Meter Ultra (https://www.decibelmeterultra.com/) if you have an iOS device. It will give you a graph over time and you can leave it running over night. Free version is limited to 2 min duration but has a 7-day free trial.
Yeah, and to stress the point: this is not "can't send vacation pictures to my grandma" bad, this is "might lose my company/my job and my house" bad, as everything else in life treats one's email (and increasingly, app 2FA) as infallible backup.
Literally every study. They will remove a particular earth moment because “it’s not relevant” but adding it in makes their data look like global warming isn’t happening. Or they exclude periods claiming that the data from that period is not good when it goes against their claims.
Here's one! (different character, but same issue it seems?)
https://www.reddit.com/r/linuxquestions/comments/1cbarz5/ele...
> and I'd love to to hunt this down and fix it but have no clue where to start. I guess the first step would be to consistently reproduce the bug...
I am not familiar with Chromium at all, and I also don't run Linux on the desktop as I'm guessing from your video you do (?) so take this with a grain of salt...
I would start looking at the focus and key event handlers. e.g. maybe log the contents of pressed_keys and/or step thru the code from the beginning of the focus handler. It looks like this might be the place:
https://github.com/chromium/chromium/blob/01ab59ae08a38a361d...
https://github.com/chromium/chromium/blob/de351fd416ec36beeb...
Even if you can't repro it, you may be able to figure out the issue by just reading thru that code with some theories in mind. e.g. Since pressing another key seems to fix it, maybe look at what the code is doing there... my guess is the release event fixes whatever corrupted state it is in upon focus.