Background Features in Google Meet, Powered by Web ML

Re:Background Features in Google Meet, Powered by Web ML by Spare_account on Monday November 02, 2020 @03:11AM (#24965672)

I've often thought that on a touch screen device the OS should ignore touches on buttons/popups that have been on screen for less time than a human could reasonably have observed it and chosen to interact with it. If I touch the screen 0.05 seconds after a button appears, I was probably _not_ aiming for that button.

In fact, now I think about it, this has happened many times over the years with traditional mouse drive interfaces too.

I'm sure some power users would like to shorten the 'reaction time delay' or even remove it entirely so I guess that should be an option as well.

[ Parent | on HN ]

Re:Background Features in Google Meet, Powered by Web ML by XorNot on Monday November 02, 2020 @03:47AM (#24965885)

Honestly with mouse driven interfaces the rule should be that whatever is popping up on screen absolutely cannot put an interactable control under the current mouse cursor location, and no control should have control focus by default.

There's nothing quite like watching a dialog box go flying by because you hit enter at the exact moment it popped up. What was it? What did it do? We'll never know!

[ Parent | on HN ]

Re:Background Features in Google Meet, Powered by Web ML by therealcamino on Monday November 02, 2020 @11:12AM (#24969649)

My "favorite" instance of that, many years ago, was when the dialog turned out to have said, "Reboot the computer immediately because IT has installed new software." I filed a ticket on that one.

[ Parent | on HN ]

Re:Background Features in Google Meet, Powered by Web ML by folmar on Monday November 02, 2020 @04:56PM (#24973914)

As a "power user" I totally disdain the idea. I know what will appear in programs I use often and touch without waiting for the button to be drawn.

[ Parent | on HN ]