Post

But some people on X pointed that Apple doesn’t respect this guideline. Or maybe a “Close” behaves differently than a “Cancel”? 🤔 What’s Apple stake on this @mikestern.bsky.social? Could you please specify in the Apple HIG if this is valid for both Close and Cancel? Thanks! x.com/vistar941/st...

0 reposts5 likes

Seems like there’s a difference between “close” and “cancel” where “cancel” is a destructive action with an opposite confirm button. Close is non-destructive so it stays in the primary trailing spot

Yes, close is to my knowledge trailing in as it is usually the only toolbar button. However, the button in messages is actually labeled as a cancel button when using VoiceOver (makes sense, content gets lost when closing it).

Florian@typ0genius.com

After yesterday’s example of the new button roles, I want to go a bit in depth as I mixed up a few things. With iOS 26, there are now four button roles: close and confirm (26+), destructive and cancel (15+). #iOSDev #SwiftUI

Yup, but how best to combine the ButtonRole and the ToolbarItemPlacement? Because if you use a close role in a cancellation placement, the button is on the leading edge.

I don’t think the position is determined by the ButtonRole. If I use the cancel role for example, it’s also positioned on the trailing edge of the navigation bar. Which seems to be opposite to the cancellationAction ToolbarItemPlacement.