Browser support
By , all four targets had shipped the implementation listed below. Devices still running an older browser can need a fallback.
| Browser | Version | Release date |
|---|---|---|
| Chrome | 1 | 2008-12-11 |
| Firefox | 1 | 2004-11-09 |
| Safari on macOS | 1 | 2003-06-23 |
| Safari on iOS | 1 | 2007-06-29 |
Check your rollout target
What to test before release
Run the user journey that reaches Element.tagName on your oldest supported browser. Test what the user sees if that member is unavailable. Record whether the task still finishes, which fallback ran, and whether the result was saved correctly.
The table describes implementation availability. Device capabilities, the execution context, and user permissions can affect runtime behavior. Read the MDN reference for tagName.
More from Element
Growth Purple engineering reference. Version comparisons use MDN Browser Compatibility Data v8.1.10, snapshot 2026-11-19, released under CC0.