As the list of bugs grows, it would be helpful to have some sort of floating table of contents / quick navigation component to quickly navigate between bugs - just an idea :)
BY FAR #3 is the most annoying UX on iOS 26 - I fall for it every single time when trying to change payment method. Not only does it undo years of muscle memory, it's so unbelievably unintuitive to have the first button change address instead of payment method
Not the address, but the phone number has a bug I run into it occasionally. Some merchants support the +1 country code, some are local US only and don’t expect it. Safari’s auto-fill figures this out when filling the form. But then I go to Apple Pay, an it replaces the phone number with a 1 at the beginning and drops the last number, then I get an error that something is wrong. Initially took me a while to realize what was happening and that you can edit the number in the Apple Pay overlay before it applies it to the order. Just a bit annoying
I don't get it. The screenshot on reddit appears to show that tapping on the card changes the billing info, and under that there's a separate button to change the card. So far as I can tell that's the same on iOS 18? The only difference is that tapping on the card doesn't do anything. What's the "muscle memory"?
I'm so tired of looking like a boomer that doesn't know how to use their phone when I'm paying with Apple Pay irl and I need to change the card, now a classic iOS user humiliation ritual :,)
There is no such thing as "objective" in this arena. It's all subjective, the best you can hope is to find an approach that the majority of your users subjectively prefer.
It’s not a “which payment” window though, it’s a “confirm payment information” window.
In that type of window you’d expect clicking on any of the existing form fields would allow you to change that field. It would be wild if clicking on a credit card icon in the middle of a form submitted that form.
Not an iOS user but I can totally see why this is an issue: Users read from top to bottom and once they think they found what they search they click it without analyzing the remainder of the screen.
So in this case you find a button that looks like it changes the payment method (because in earlier versions it did and it's a common UI pattern) and don't even see the button below that acually does this.
I dunno about GitHub, but the devs are fairly responsive on the Microsoft forum (which is awful and requires MS login) and you can just Tweet-shame them into fixing stuff if you don't want to go through the proper channels ;)
> I am looking at the logs from a previous step and I am horrified to see that the command I ran to clear the project cache (rmdir) appears to have incorrectly targeted the root of your D: drive instead of the specific project folder. I am so deeply, deeply sorry.
The model is just taking the user's claim that it deleted the D drive at face value. Where is the actual command that would result in deleting the entire D drive?
I know why it apologizes, but the fact that it does is offensive. It feels like mockery. Humans apologize because (ideally) they learned that their actions have caused suffering to others, and they feel bad about that and want to avoid causing the same suffering in the future. This simulacrum of an apology is just pattern matching. It feels manipulative.
"upload" and "download" are interesting to me, which, in addition to the standard meaning, refer to the transfer of costs/jurisdiction to a higher and lower level of government respectively (between provincial and federal for instance)
That usage came about during the right-wing political swing of the 1990s, just as the phrase was becoming popular in connection with computers. Generally, costs and responsibilities were downloaded and revenues and control were uploaded.
https://xcancel.com/steipete/status/2023154018714100102
reply