Action Sheet

An action row takes the full inline size of the sheet with its label centred, so it has no start and no end to swap, and UIAlertAction gives you no alignment knob anyway. The risk is in hand-written versions: text-align: left inside a row leaves the Arabic label hanging on the left after the rest of the screen has flipped. Write text-align: center to match the iOS form, or text-align: start if you align the names to the beginning of the line the way Material list rows do.

Where a row does carry an icon before its name, as in Material list rows or a hand-written web sheet, that icon belongs at the logical start and lands on the right of the row in Arabic. Build the row with flex, gap, and padding-inline-start, never padding-left or margin-right, and remember that on Android nothing moves until android:supportsRtl="true" is in the manifest. Only a directional glyph also flips its own drawing: take those from Icons.AutoMirrored in Compose or from imageFlippedForRightToLeftLayoutDirection() in UIKit, and leave the trash can and the share glyph alone.

Nothing about the destructive row mirrors: the red is a state rather than a direction, and its slot at the top of the sheet is the same in both languages. Row order runs down the block axis, which direction never touches, so flex-direction: column-reverse has no business anywhere near this list. The recurring mistake is a blanket [dir="rtl"] svg { transform: scaleX(-1) }, which flips the trash glyph with everything else and leaves it drawn back to front; transform has no logical counterpart, so scope that rule to the icons that really are directional.

The tablet form grows out of whatever opened it, so it follows that control's logical side: a button at the end of the navigation bar opens the popover on the left in Arabic after opening on the right in English. The trap is sourceRect, a physical CGRect in the source view's own coordinate space, so CGRect(x: view.bounds.width - 44, …) stays pinned to the right whatever the interface direction is. Pass sourceItem or barButtonItem and let UIKit compute the frame, or read view.effectiveUserInterfaceLayoutDirection and mirror x yourself. permittedArrowDirections is physical in the same way, since .left and .right have no logical twin, so swap them with the direction or settle for .any.

Arabic does not track English length: «حذف» is half of Delete in characters, while «إضافة إلى الشاشة الرئيسية» runs a third longer than Add to Home Screen. The native sheet wraps a long title onto a second line and grows the row, and hand-written versions break that with a fixed row height, with white-space: nowrap plus text-overflow: ellipsis, or with maxLines = 1 in Compose. Swap height for min-block-size and leave the label wrapping, because clipping the end of an Arabic command drops its object, the part that says what the command acts on. Arabic also needs a taller line box than Latin at the same size, so a line-height tuned on English clips the descenders of ج and ح and the dots under ي.