Overview
Microsoft's Windows 11 update has adopted the Tab key for navigating between fields in dialog boxes, a decision that directly contradicts IBM's original specification for OS/2. The change, documented in a recent post on Microsoft's Old New Thing blog by Raymond Chen, reveals a long-standing cultural clash between the two companies during their collaboration on OS/2 in the late 1980s.
What happened
During the OS/2 partnership, Microsoft developers working at IBM's Boca Raton, Florida offices chose the Tab key to move between dialog fields. IBM objected, arguing that the Tab key should be reserved for tabbing between form fields—a convention IBM had specified. The dispute escalated through multiple management levels at IBM, eventually reaching a vice president who was "absolutely opposed" to using Tab for this purpose.
Microsoft's response, relayed by a manager in Redmond, was blunt: "The reason you are in Boca is to make these decisions so I don't have to be in Boca." After IBM's VP-level escalation, the Microsoft manager replied, "Bill Gates's mother is not interested in the Tab key." That ended the discussion, and the Tab key remained in use.
Why it matters
The Tab key's role in dialog navigation is now a decades-old convention in Windows. The recent Windows 11 update formalizes this choice, affecting both developers building dialog-based UIs and users who rely on keyboard navigation. For accessibility, the change means that users who navigate dialogs via keyboard will continue to use Tab to move between fields—consistent with Windows behavior since the OS/2 era.
Tradeoffs
The decision has implications for consistency across platforms. On macOS and many Linux desktop environments, Tab typically moves between all focusable controls in a dialog, while Shift+Tab moves backward. Windows 11's approach aligns with this broader convention, but it differs from IBM's original specification, which reserved Tab for tab stops within a single form field. Developers building cross-platform applications may need to account for this difference.
Bottom line
The Tab key's role in Windows dialog navigation is a legacy of a corporate dispute resolved by a memorable one-liner. The Windows 11 update confirms that Microsoft's choice from the OS/2 era remains the standard, overriding IBM's original specification. For users and developers, the practical takeaway is simple: Tab moves between dialog fields, and Shift+Tab moves backward—a convention that has held for over three decades.