Live data from Hacker News

Mac: Keyboard Shortcuts Killed by Bug

eclecticlight.co

11–20 of 119 posts

Re: Mac: Keyboard Shortcuts Killed by Bug

#11
> This isn’t a subtle bug which only occurs in certain circumstances.

Sure it is. OP is an outlier in how they use this panel. Most people just use it to enable/disable the built-in menu commands, or to modify their accelerators.

One very common use-case for people who speak multiple languages is enabling the keyboard switcher accelerator. I expect that they have extensive tests for common use-cases like that.

On the other hand, I expect that the test suite they use probably only tests creating one or two custom keyboard shortcuts using the panel; and doesn’t give them overly-long names. UX integration tests, above the level of the control library itself, aren’t usually concerned with being fuzz tests on what happens when you have a whole bunch of something (long strings, many items) loaded into a control. Normally the control library itself takes care of that for you (and has its own trustworthy fuzzing/property-testing suite), so you only worry about ensuring that your view controller gets the data into the control’s data binding in the right way.

I would guess that this bug is there because the view controller is summing up the lengths of the strings under a given section for some task; and then, later on, accidentally using that sum-of-lengths as the determinant for whether each string is too long to fit into its column and needs ellipsis...ing (eliding? elision?), rather than using each individual key’s length. Totally plausible bug, it makes total sense that this is an old bug that nobody discovered until now. It would seem that literally nobody has tried to do this until now.

Still, this is the type of thing that’ll get fixed immediately if you file a Radar on it. Whatever the underlying problem is, it’s on the view-controller layer, and definitely a simple fix; and there’s no decisions or opinion required on what the fix should be; and it doesn’t require any specific expertise (like having knowledge of the kernel.) It’s an “easy win” ticket someone would likely knock out the same day you submitted it.

The fact that it didn’t get caught during any of the numerous betas since Sierra, really, really implies that nobody ever thought to try this—users or developers. (Because if someone did report this bug in the beta, and it was still in the prod release, you can bet they would have blogged about it when that happened.)

Re: Mac: Keyboard Shortcuts Killed by Bug

#12
post #7

Bug aside, this from-the-outside-in way of creating keyboard shortcuts is a cool feature, that I bet a minority of even Mac powerusers are aware of. See also "DefaultKeyBinding.dict" for more keyboard behavior possibilities, including stuff like ^W and ^U working in Cocoa text fields.

One great thing about macOS is that Apple provides a couple of tools to extend existing apps. The other really great one is Automator Services/Quick Actions.

Re: Mac: Keyboard Shortcuts Killed by Bug

#13
Tangent (or OT), something I've been struggling with as a new macOS user, how do I get keyboard repeats working? I understand they removed repeats so that a long press can offer accent characters.

I've done `defaults write -g KeyRepeat -int 5` or something like that and it kinda works but somehow doesn't feel "right" still. Am I missing something obvious?

Re: Mac: Keyboard Shortcuts Killed by Bug

#14

Tangent (or OT), something I've been struggling with as a new macOS user, how do I get keyboard repeats working? I understand they removed repeats so that a long press can offer accent characters. I've done `defaults write -g KeyRepeat -int 5` or something like that and it kinda works but somehow doesn't feel "right" still. Am I missing something obvious?

I haven't experienced your problem on my Mac, but you might try adjusting InitialKeyRepeat, too. I believe the old default was 15 (225 ms). (The old default for KeyRepeat was 2 (30 ms).)

Re: Mac: Keyboard Shortcuts Killed by Bug

#15
My complaint about this preferene pane - no wildcards in menu names.

macOS has a handy "Batch rename" feature in the contextual menu when you right click on files. The renaming GUI gives you options for sequential numbers, text replacement, prefixes, suffixes, inserting dates.

But the menu to open this is called "Rename X Items…" so you can't assign a keyboard shortcut to it. Might be 5 items, might be 2914 items. Without wildcards you'd have to make a different shortcut for every different quantity.

Re: Mac: Keyboard Shortcuts Killed by Bug

#16
post #4

It's a bug for sure, but conclusions like this are over the top for a single small bug: > This isn’t an Apple which has any concern over the quality of its products, or for its users. It’s just another leviathan corporation which has stopped caring or taking pride. One small bug reveals a deep and pervasive problem. I'd rather see a more measured approach to drawing conclusions from a single anecdote.

I completely agree. No one sets out to create bugs in their software. I'd give the engineers working on this the benefit of the doubt versus a grand conspiracy of product apathy.

Re: Mac: Keyboard Shortcuts Killed by Bug

#17
post #4

It's a bug for sure, but conclusions like this are over the top for a single small bug: > This isn’t an Apple which has any concern over the quality of its products, or for its users. It’s just another leviathan corporation which has stopped caring or taking pride. One small bug reveals a deep and pervasive problem. I'd rather see a more measured approach to drawing conclusions from a single anecdote.

If this was the only item, I would agree with you, but it isn't. Finder is buggy and broken since Mavericks (along with some bugs that look like the got rebroke in [edit]10.14[/edit]). Each new version of Mac OS breaks more stuff. This is exacerbated by their hardware failures and constant "only affects a small number of users" line that gets old. Its a constant stream of breaks these days and they need to start look…

My 2012 MacBook Pro Retina has been more stable on Mojave than on any previous OS. It used to crash at least once a week; at the moment `uptime` tells me it's been 21 days since a reboot.

I attribute this to improvements in the reliability of Airplay: my machine used to be prone to crashing after connecting via Airplay (either sound only or mirroring) to my old Apple TV.

I'm sure other things have been broken along the way, but it seems to me like Apple is tackling hard problems at the OS level and making progress.

Re: Mac: Keyboard Shortcuts Killed by Bug

#18
post #2

Apple used to be pretty good with Mac accessibility. Now, not so much.

And overall power usage. I think I probably know more shortcuts and optimizations on macOS than most people at Apple.

Have any tricks you want to share? My MBP 15" gets 2 hr tops unless its plugged in. Even with "mere" web browsing

Re: Mac: Keyboard Shortcuts Killed by Bug

#19
This bug is much more subtle that the author describes. I use keyboard shortcuts semi-regularly so I would've noticed this bug, especially if it had been around since 10.13. I never noticed it, but then I realized the author's screenshots are all dark themed. I use the light theme and cannot reproduce it under 10.14.4 with light theme.

If I toggle to dark theme, I can reproduce it, but not in a consistent way. Depending upon how I add and remove shortcuts and toggle themes, I can get just the last shortcut to display incorrectly, or all of them to display incorrectly, or none of them to. It's some odd interaction between dark/light themes and this panel.

Re: Mac: Keyboard Shortcuts Killed by Bug

#20
post #4

It's a bug for sure, but conclusions like this are over the top for a single small bug: > This isn’t an Apple which has any concern over the quality of its products, or for its users. It’s just another leviathan corporation which has stopped caring or taking pride. One small bug reveals a deep and pervasive problem. I'd rather see a more measured approach to drawing conclusions from a single anecdote.

Straws break camel's backs. You can be sure this isn't the only, the first, or even the last time this particular developer has found a major bug. It's also safe to assume that past bugs they have reported (especially small usability bugs like this) have languished, or been closed as "will not fix".

At some point, the back is broken, the developer gives up on trying to help an obscenely profitable company QA their own products, and rants about the lack of care being shown.

Post reply on HN