|
|
|
|
|
by bartread
1311 days ago
|
|
1) Yes, people use tweets to report bugs all the time. The problem with nitpicking is that anyone can pick your nits back, which leads me to... 2) Yes, they will, but that won't necessarily repro the bug without knowing which type of device it's running on, so at the very least they might need to check several different devices, and even then other factors can come into play that go beyond basic device configuration. I'm sure, given that this appears to affect at least a significant minority of users, that Apple will be all over it and will find a way to repro it in relatively short order. Yet, at the same time, it's obscure enough to have escaped their no doubt reasonably robust QA processes before release, so it may well be there are some wrinkles to reproduction that aren't immediately apparent. |
|
People might. This one didn't even @ Apple. Jesus, HN (a sentiment the Tweet author has also expressed by now on the tweet thread, as they're apparently reading this and seeing y'all acting like this in public)
> 2) Yes, they will, but that won't necessarily repro the bug without knowing which type of device it's running on, so at the very least they might need to check several different devices, and even then other factors can come into play that go beyond basic device configuration.
Twitter figured this out in like 30 minutes. It's Safari Suggestions on any recent iOS. This may not be the platonic ideal of a bug report but it's not a bug report and also it happens, by chance, to be entirely fine even if it were, because this is super-easy to figure out.