3 ms·

That doesn't seem like the root cause to me. It sounds like they have events set up for the UI prior to login which doesn't really make sense. The regression in

That doesn't seem like the root cause to me. It sounds like they have events set up for the UI prior to login which doesn't really make sense. The regression in Catalina may have exposed it but the regression is not the cause of this, as far as I can tell.

shawnz 7y ago
While you may not believe they made the best design choice, there's nothing functionally wrong about the choice they made. According to the docs, their method should work just the same. So I don't think it's fair to say that's the cause of the bug.
- dkonofalski 7y ago
  >nothing functionally wrong about the choice they made Sure there is... The app would capture those as shortcuts instead of as user input. You know...exactly what's happening here. If this interferes with writing tweets also then that should be easy to figure out. As I said above, I'm not saying it's not because of the regression but it's more likely to me that Twitter messed it up. Otherwise, why is no other app experiencing this issue if it was done "according to the docs".
  - shawnz 7y ago
    > Otherwise, why is no other app experiencing this issue if it was done "according to the docs". Well, like you say, it's not common to use shortcut keys without modifiers right? So it doesn't seem that surprising to me that nobody noticed the regression.
userbinator 7y ago
At (the old) Microsoft, that would absolutely be considered a regression --- code that used to work no longer does. https://devblogs.microsoft.com/oldnewthing/20031224-00/?p=41363 https://devblogs.microsoft.com/oldnewthing/20031224-00/?p=41... As Linus Torvalds would say, "WE DO NOT BREAK USERSPACE!"
- giovannibajo1 7y ago
  The application is brand new, and is built on a brand new macOS API. Nobody broke anything. The point is whether the bug is due to Twitter’s usage of the APIs, or the APIs themselves.

3 ms·

That doesn't seem like the root cause to me. It sounds like they have events set up for the UI prior to login which doesn't really make sense. The regression in

by dkonofalski 7y ago

shawnz 7y ago
While you may not believe they made the best design choice, there's nothing functionally wrong about the choice they made. According to the docs, their method should work just the same. So I don't think it's fair to say that's the cause of the bug.
- dkonofalski 7y ago
  >nothing functionally wrong about the choice they made Sure there is... The app would capture those as shortcuts instead of as user input. You know...exactly what's happening here. If this interferes with writing tweets also then that should be easy to figure out. As I said above, I'm not saying it's not because of the regression but it's more likely to me that Twitter messed it up. Otherwise, why is no other app experiencing this issue if it was done "according to the docs".
  - shawnz 7y ago
    > Otherwise, why is no other app experiencing this issue if it was done "according to the docs". Well, like you say, it's not common to use shortcut keys without modifiers right? So it doesn't seem that surprising to me that nobody noticed the regression.
userbinator 7y ago
At (the old) Microsoft, that would absolutely be considered a regression --- code that used to work no longer does. https://devblogs.microsoft.com/oldnewthing/20031224-00/?p=41363 https://devblogs.microsoft.com/oldnewthing/20031224-00/?p=41... As Linus Torvalds would say, "WE DO NOT BREAK USERSPACE!"
- giovannibajo1 7y ago
  The application is brand new, and is built on a brand new macOS API. Nobody broke anything. The point is whether the bug is due to Twitter’s usage of the APIs, or the APIs themselves.