3 ms·
I wanted to love the touch bar, but the current implementation is a failure -- it needs to be pressure sensitive. A light brushing of a physical key doesn't reg
by bonestamp2 6y ago
I wanted to love the touch bar, but the current implementation is a failure -- it needs to be pressure sensitive. A light brushing of a physical key doesn't register and a good implementation of the touch bar would behave the same way.
In the meantime, I would pay extra to the replace the touch bar with the physical buttons we used to have. I've gotten so tired of accidentally hitting the touch bar that I have disabled it as much as possible -- I have it configured so holding the fn button brings it back, making it much more difficult to accidentally trigger something. Of course, as the article mentions, this makes it even more difficult to trigger the sound controls when they're uncomfortably loud, but that's still a trade off I'm willing to make to avoid so many false positive interactions with the touch bar.
- grishka 6y agoAlso the delay the author mentions seems to be related to the touch bar. I have a 2012 macbook with actual physical buttons where the touch bar would be, and hitting F10 mutes the audio immediately. The bigger problem, though, is that modern web browsers put website developers before users. It's a user agent. It should allow the user to control everything. I honestly wish they asked for permission per-domain before a website is allowed to use <video> and <audio> tags.