sgabriel, thoughts?

Hi, thanks for the suggestion.

Always keeping track of the cursor position is one of the top priority when using mouse input. If I understand the proposal correctly here, this would go against that.
Cursor should only disappear when scrolling with fingers, showing a clear intent of the user not to use mouse input.

Fair enough, I don't think that your philosophy is wrong, however there is
some potential wiggle room in that this behavior already exists once any
key on the keyboard is hit. So there is already a case where the cursor
disappears, despite knowing the user has a mouse. It's done to get it out
of the way of where the user is looking, which is the same reasoning I had
for scrolling. Do you not find yourself more frequently scrolling then
moving the cursor off of where you scrolled? Please at least give some
thought to philosophy as to why I'm proposing the change moving forward,
even if you keep this ticket on Won'tFix. I think the concept I'm pitching
has some solution out there, if not this, as the web changes and the cursor
gets in the way more often.

I've found a lot of PWAs that have this problem if needing the cursor
covering content to scroll.

Perhaps someday a chrome:flag or A/B test to see if it actually is a
problem to hide the cursor more frequently? I suspect it won't be as
jarring as it might initially sound. It happens to every user hundreds of
times a day whenever they type on their computer. The first movement brings
the cursor right back and we all seem to handle it just fine.

A crazier idea you should totally (but I know never will A/B test haha)
would be to be very aggressive with the cursor disappearing and having it
always re-appear from the center of the screen each time. Maybe test that
one only internally haha, but I'd be very curious to find out how fast
someone could adapt to that concept.

Anyways, crazy ideas aside, please just do me the favor of at least keeping
an open mind about fading the cursor more. I know you have that internal
rule of not hiding it, but is that rule really as at important today as it
was 20 years ago? I'm not sure. I'm not saying no, but I'm also not saying
yes.

Thank you for at least commenting on this ticket, it was much appreciated.

I will keep that in mind, and the Chrome team is always thriving to make things better. Things may change over time, as you pointed out.

Thanks for the deep thinking behind this suggestion.