:type-selector

Client-by-client behaviour for :type-selector

Fully supports :type-selector (17): Gmail, Outlook 365, Outlook (New), Outlook Classic, Outlook iOS, Outlook Android, Outlook for Mac, Apple Mail, Apple Mail iOS, Yahoo Mail, Yahoo Mail Android, Yahoo Mail iOS, Samsung Mail, Thunderbird, HEY Mail, AOL Mail, Fastmail.

Partial support (2): Gmail Android, Gmail iOS. Expect rendering quirks unique to each engine. Partial support typically means a subset of values, an ignored shorthand, or sanitizer-specific rewrites.

No support (1): Proton Mail. Plan fallbacks for these clients before relying on :type-selector in production sends.

Behaviour unverified in: Superhuman.

When to use :type-selector in email

• Setting a base font-family on every <p> and <td> in the document.
• Resetting <a> color and underline globally before applying inline overrides.
• Establishing default <li> spacing for all unordered lists.

Rendering behaviour and edge cases

• Type selectors have very low specificity and are easily overridden by inline styles or class selectors.
• Outlook strips <style> blocks, so type selectors are inert there.
• Gmail honors type selectors when <style> survives but rewrites class names that interact with them.

Recommended fallback strategy

Treat type selectors in <style> as a baseline that may not apply. Always set critical typography inline on each text-bearing element. Use type selectors for non-critical refinements only.

Fixes & Workarounds