Now Stable

"New on the Web": For a given set of browsers, what APIs became stable and when, ordered reverse chronologically.

It's a great source of information for posts like this

Example Comparisons
Browsers
Features

Stable APIs

Below is a list of features that are in Chrome and Firefox, ordered reverse chronologically by when they became stable (i.e, available in the last browser).

2026/3

API First Browser Date Last Browser Date Days Notes
html.elements.template.shadowrootreferencetarget Chrome2/4/2025 Firefox3/24/2026413

2026/2

API First Browser Date Last Browser Date Days Notes
html.elements.details.search_match_opens Chrome1/4/2022 Firefox2/24/20261512
Firefox: The browser does not correctly scroll to the matching text. See bug 2006040.Firefox for Android: The browser does not correctly scroll to the matching text. See bug 2006040.Safari: The browser does not correctly scroll to the matching text. See bug 304174.Safari on iOS: The browser does not correctly scroll to the matching text. See bug 304174.WebView on iOS: The browser does not correctly scroll to the matching text. See bug 304174.
html.global_attributes.hidden.until-found 📋Chrome5/24/2022 Firefox2/24/20261372
Firefox: The browser does not correctly scroll to the matching text. See bug 2006040.Firefox for Android: The browser does not correctly scroll to the matching text. See bug 2006040.Safari: The browser does not correctly scroll to the matching text. See bug 304174.Safari on iOS: The browser does not correctly scroll to the matching text. See bug 304174.WebView on iOS: The browser does not correctly scroll to the matching text. See bug 304174.

2026/1

API First Browser Date Last Browser Date Days Notes
html.elements.button.commandfor.implicit_anchor_reference 📋Chrome4/1/2025 Firefox1/13/2026287
html.elements.button.popovertarget.implicit_anchor_reference 📋Chrome2/4/2025 Firefox1/13/2026343
html.elements.input.popovertarget.implicit_anchor_reference 📋Chrome2/4/2025 Firefox1/13/2026343

2025/10

API First Browser Date Last Browser Date Days Notes
html.elements.button.command 📋Chrome4/1/2025 Firefox10/14/2025196
html.elements.button.command.request-close 📋Chrome8/5/2025 Firefox10/14/202570
html.elements.button.commandfor 📋Chrome4/1/2025 Firefox10/14/2025196
html.elements.iframe.cross-origin-top-navigation-by-user-activation Chrome7/24/2018 Firefox10/14/20252639
Chrome: If a top-navigation is blocked, users are prompted for permission to redirect, and an error is reported in the developer console.Chrome Android: If a top-navigation is blocked, users are prompted for permission to redirect, and an error is reported in the developer console.Edge: If a top-navigation is blocked, users are prompted for permission to redirect, and an error is reported in the developer console.Firefox: If a top-navigation is blocked, users are prompted for permission to redirect, and an error is reported in the developer console.Firefox for Android: If a top-navigation is blocked, users are prompted for permission to redirect, and an error is reported in the developer console.Quest Browser: If a top-navigation is blocked, users are prompted for permission to redirect, and an error is reported in the developer console.Opera: If a top-navigation is blocked, users are prompted for permission to redirect, and an error is reported in the developer console.Opera Android: If a top-navigation is blocked, users are prompted for permission to redirect, and an error is reported in the developer console.Safari: If a top-navigation is blocked, no redirect occurs, and an error is reported in the developer console.Safari on iOS: If a top-navigation is blocked, no redirect occurs, and an error is reported in the developer console.Samsung Internet: If a top-navigation is blocked, users are prompted for permission to redirect, and an error is reported in the developer console.WebView Android: If a top-navigation is blocked, users are prompted for permission to redirect, and an error is reported in the developer console.WebView on iOS: If a top-navigation is blocked, no redirect occurs, and an error is reported in the developer console.

2025/7

API First Browser Date Last Browser Date Days Notes
html.elements.dialog.closedby 📋Chrome3/4/2025 Firefox7/22/2025140

2025/4

API First Browser Date Last Browser Date Days Notes
html.elements.script.type.importmap.integrity 📋Chrome7/23/2024 Firefox4/29/2025280

2025/3

API First Browser Date Last Browser Date Days Notes
html.global_attributes.contenteditable.plaintext-only Chrome5/25/2016 Firefox3/4/20253205

2024/10

API First Browser Date Last Browser Date Days Notes
html.elements.img.fetchpriority 📋Chrome4/26/2022 Firefox10/29/2024917
html.elements.link.fetchpriority 📋Chrome4/26/2022 Firefox10/29/2024917
html.elements.script.fetchpriority 📋Chrome4/26/2022 Firefox10/29/2024917
html.elements.a.text_fragments Chrome2/4/2020 Firefox10/1/20241701

2024/9

API First Browser Date Last Browser Date Days Notes
html.elements.details.name Chrome12/5/2023 Firefox9/3/2024273

2024/6

API First Browser Date Last Browser Date Days Notes
html.elements.base.href.forbid_data_javascript_urls Chrome4/19/2017 Firefox6/11/20242610
html.elements.link.rel.dns-prefetch 📋Chrome10/13/2015 Firefox6/11/20243164
Firefox: Only HTTP pages were supported.Firefox for Android: Only HTTP pages were supported.

2024/5

API First Browser Date Last Browser Date Days Notes
html.elements.iframe.allow.screen-wake-lock 📋Chrome7/27/2020 Firefox5/14/20241387

2024/4

API First Browser Date Last Browser Date Days Notes
html.elements.button.popovertarget 📋Chrome5/30/2023 Firefox4/16/2024322
html.elements.button.popovertargetaction 📋Chrome5/30/2023 Firefox4/16/2024322
html.elements.input.popovertarget 📋Chrome5/30/2023 Firefox4/16/2024322
html.elements.input.popovertargetaction 📋Chrome5/30/2023 Firefox4/16/2024322
html.elements.input.type_range.vertical_orientation Firefox11/21/2023 Chrome4/16/2024147
Chrome: Vertical orientation available via the writing-mode property (see Creating vertical controls).Chrome: Vertical orientation available by setting the non-standard -webkit-appearance: slider-vertical style on the input element. You shouldn't use this, since it's proprietary, unless you include appropriate fallbacks for users of other browsers.Chrome Android: Vertical orientation available via the writing-mode property (see Creating vertical controls).Chrome Android: Vertical orientation available by setting the non-standard -webkit-appearance: slider-vertical style on the input element. You shouldn't use this, since it's proprietary, unless you include appropriate fallbacks for users of other browsers.Edge: Vertical orientation available by setting the writing-mode: bt-lr style on the input element.Firefox: Vertical orientation available via the writing-mode property (see Creating vertical controls).Firefox: Supported using the non-standard orient="vertical" attribute.Firefox for Android: Vertical orientation available via the writing-mode property (see Creating vertical controls).Firefox for Android: Supported using the non-standard orient="vertical" attribute.Internet Explorer: Vertical orientation available by setting the writing-mode: bt-lr style on the input element.Quest Browser: Vertical orientation available by setting the non-standard -webkit-appearance: slider-vertical style on the input element. You shouldn't use this, since it's proprietary, unless you include appropriate fallbacks for users of other browsers.Opera: Vertical orientation available via the writing-mode property (see Creating vertical controls).Opera: Vertical orientation available by setting the non-standard -webkit-appearance: slider-vertical style on the input element. You shouldn't use this, since it's proprietary, unless you include appropriate fallbacks for users of other browsers.Opera Android: Vertical orientation available via the writing-mode property (see Creating vertical controls).Opera Android: Vertical orientation available by setting the non-standard -webkit-appearance: slider-vertical style on the input element. You shouldn't use this, since it's proprietary, unless you include appropriate fallbacks for users of other browsers.Safari: Vertical orientation available via the writing-mode property (see Creating vertical controls).Safari: Vertical orientation available by setting the non-standard -webkit-appearance: slider-vertical style on the input element. You shouldn't use this, since it's proprietary, unless you include appropriate fallbacks for users of other browsers.Safari on iOS: Vertical orientation available via the writing-mode property (see Creating vertical controls).Safari on iOS: Vertical orientation available by setting the non-standard -webkit-appearance: slider-vertical style on the input element. You shouldn't use this, since it's proprietary, unless you include appropriate fallbacks for users of other browsers.Samsung Internet: Vertical orientation available via the writing-mode property (see Creating vertical controls).Samsung Internet: Vertical orientation available by setting the non-standard -webkit-appearance: slider-vertical style on the input element. You shouldn't use this, since it's proprietary, unless you include appropriate fallbacks for users of other browsers.WebView Android: Vertical orientation available via the writing-mode property (see Creating vertical controls).WebView Android: Vertical orientation available by setting the non-standard -webkit-appearance: slider-vertical style on the input element. You shouldn't use this, since it's proprietary, unless you include appropriate fallbacks for users of other browsers.WebView on iOS: Vertical orientation available via the writing-mode property (see Creating vertical controls).WebView on iOS: Vertical orientation available by setting the non-standard -webkit-appearance: slider-vertical style on the input element. You shouldn't use this, since it's proprietary, unless you include appropriate fallbacks for users of other browsers.
html.elements.template.shadowrootclonable 📋Chrome4/16/2024 Firefox4/16/2024
html.global_attributes.inert.ignores_find_in_page 📋Firefox11/21/2023 Chrome4/16/2024147
html.global_attributes.popover 📋Chrome5/30/2023 Firefox4/16/2024322

2024/3

API First Browser Date Last Browser Date Days Notes
html.elements.template.shadowrootdelegatesfocus 📋Firefox2/20/2024 Chrome3/19/202428

2024/2

API First Browser Date Last Browser Date Days Notes
html.elements.template.shadowrootmode 📋Chrome3/7/2023 Firefox2/20/2024350

2024/1

API First Browser Date Last Browser Date Days Notes
html.elements.form.autocomplete.webauthn 📋Chrome11/29/2022 Firefox1/23/2024420
html.elements.hr.hr_in_select Chrome10/31/2023 Firefox1/23/202484
Chrome: Exposes the <hr> visually in the page only when the menu is expanded (arrowing within the collapsed menu does not show them).Chrome: Does not expose the <hr> in the accessibility tree.Edge: Exposes the <hr> visually in the page only when the menu is expanded (arrowing within the collapsed menu does not show them).Edge: Does not expose the <hr> in the accessibility tree.Firefox: Does not expose the <hr> in the accessibility tree.Opera: Exposes the <hr> visually in the page only when the menu is expanded (arrowing within the collapsed menu does not show them).Opera: Does not expose the <hr> in the accessibility tree.Safari: Does not expose the <hr> in the accessibility tree.Safari on iOS: Does not expose the <hr> in the accessibility tree.WebView on iOS: Does not expose the <hr> in the accessibility tree.
html.elements.select.hr_in_select Chrome10/31/2023 Firefox1/23/202484
Chrome: Exposes the <hr> visually in the page only when the menu is expanded (arrowing within the collapsed menu does not show them).Chrome: Does not expose the <hr> in the accessibility tree.Edge: Exposes the <hr> visually in the page only when the menu is expanded (arrowing within the collapsed menu does not show them).Edge: Does not expose the <hr> in the accessibility tree.Firefox: Does not expose the <hr> in the accessibility tree.Opera: Exposes the <hr> visually in the page only when the menu is expanded (arrowing within the collapsed menu does not show them).Opera: Does not expose the <hr> in the accessibility tree.Safari: Does not expose the <hr> in the accessibility tree.Safari on iOS: Does not expose the <hr> in the accessibility tree.WebView on iOS: Does not expose the <hr> in the accessibility tree.
html.elements.video.disablepictureinpicture 📋Chrome9/4/2018 Firefox1/23/20241967
Firefox: When this attribute is set, the overlay button to disable picture-in-picture (PiP) is hidden, but the user can still enable PiP.Firefox: When this attribute is set, the overlay button to disable picture-in-picture (PiP) is hidden, but the user can still enable PiP.Firefox for Android: When this attribute is set, the overlay button to disable picture-in-picture (PiP) is hidden, but the user can still enable PiP.Firefox for Android: When this attribute is set, the overlay button to disable picture-in-picture (PiP) is hidden, but the user can still enable PiP.

2023/12

API First Browser Date Last Browser Date Days Notes
html.elements.iframe.loading 📋Chrome9/10/2019 Firefox12/19/20231561

2023/10

API First Browser Date Last Browser Date Days Notes
html.elements.search 📋Firefox9/26/2023 Chrome10/10/202314

2023/9

API First Browser Date Last Browser Date Days Notes
html.elements.iframe.allow.publickey-credentials-get 📋Chrome7/27/2020 Firefox9/26/20231156

2023/8

API First Browser Date Last Browser Date Days Notes
html.elements.input.dirname 📋Chrome2/8/2012 Firefox8/1/20234192
html.elements.textarea.dirname 📋Chrome2/8/2012 Firefox8/1/20234192

2023/7

API First Browser Date Last Browser Date Days Notes
html.elements.link.rel.modulepreload 📋Chrome4/17/2018 Firefox7/4/20231904
html.elements.link.rel.modulepreload.as-script 📋Chrome4/17/2018 Firefox7/4/20231904

2023/5

API First Browser Date Last Browser Date Days Notes
html.elements.iframe.sandbox.allow-storage-access-by-user-activation Firefox1/29/2019 Chrome5/2/20231554

2023/4

API First Browser Date Last Browser Date Days Notes
html.global_attributes.inert 📋Chrome5/24/2022 Firefox4/11/2023322

2023/3

API First Browser Date Last Browser Date Days Notes
html.elements.form.rel 📋Chrome11/29/2022 Firefox3/14/2023105
html.global_attributes.autocapitalize 📋Chrome5/19/2015 Firefox3/14/20232856
html.global_attributes.translate 📋Chrome5/15/2012 Firefox3/14/20233955

2023/2

API First Browser Date Last Browser Date Days Notes
html.elements.datalist.input_type_range 📋Chrome6/26/2012 Firefox2/14/20233885
html.elements.input.type_range.list 📋Chrome6/26/2012 Firefox2/14/20233885
html.global_attributes.autofocus 📋Chrome12/10/2019 Firefox2/14/20231162
Chrome: Supported for the <button>, <input>, <select>, and <textarea> elements.Chrome Android: Supported for the <button>, <input>, <select>, and <textarea> elements.Edge: Supported for the <button>, <input>, <select>, and <textarea> elements.Firefox: Supported for the <button>, <input>, <select>, and <textarea> elements.Firefox for Android: Supported for the <button>, <input>, <select>, and <textarea> elements.Internet Explorer: Supported for the <button>, <input>, <select>, and <textarea> elements.Quest Browser: Supported for the <button>, <input>, <select>, and <textarea> elements.Opera: Supported for the <button>, <input>, <select>, and <textarea> elements.Opera Android: Supported for the <button>, <input>, <select>, and <textarea> elements.Safari: Supported for the <button>, <input>, <select>, and <textarea> elements.Safari on iOS: If there's no hardware keyboard connected, then the autofocus attribute has no effect (for example, the focus event doesn't fire and the element does not match the :focus selector).Samsung Internet: Supported for the <button>, <input>, <select>, and <textarea> elements.WebView Android: Supported for the <button>, <input>, <select>, and <textarea> elements.WebView on iOS: If there's no hardware keyboard connected, then the autofocus attribute has no effect (for example, the focus event doesn't fire and the element does not match the :focus selector).

2023/1

API First Browser Date Last Browser Date Days Notes
html.elements.form.autocomplete.one-time-code Chrome8/31/2021 Firefox1/17/2023504
html.elements.input.type_range.tick_marks Chrome5/29/2018 Firefox1/17/20231694
html.elements.textarea.autocomplete.one-time-code Chrome8/31/2021 Firefox1/17/2023504

2022/12

API First Browser Date Last Browser Date Days Notes
html.elements.script.type.importmap 📋Chrome3/2/2021 Firefox12/13/2022651
html.elements.source.height 📋Chrome4/13/2021 Firefox12/13/2022609
html.elements.source.width 📋Chrome4/13/2021 Firefox12/13/2022609

2022/3

API First Browser Date Last Browser Date Days Notes
html.elements.dialog 📋Chrome8/26/2014 Firefox3/8/20222751
html.elements.dialog.open Chrome8/26/2014 Firefox3/8/20222751

2022/1

API First Browser Date Last Browser Date Days Notes
html.elements.meta.name.color-scheme 📋Chrome4/7/2020 Firefox1/11/2022644

2021/12

API First Browser Date Last Browser Date Days Notes
html.global_attributes.inputmode 📋Chrome4/17/2018 Firefox12/7/20211330
Safari on iOS: Before iOS 13, inputmode="none" had no effect.WebView on iOS: Before iOS 13, inputmode="none" had no effect.

2021/11

API First Browser Date Last Browser Date Days Notes
html.global_attributes.enterkeyhint 📋Chrome9/10/2019 Firefox11/2/2021784

2021/10

API First Browser Date Last Browser Date Days Notes
html.elements.input.type_datetime-local 📋Chrome6/26/2012 Firefox10/5/20213388
Firefox: Only displays a date picker without a time picker, see bug 1726107 and bug 1726108.Firefox for Android: Only displays a date picker without a time picker, see bug 1726107 and bug 1726108.Safari: Safari only displays a date picker and does not display a time picker.

2021/9

API First Browser Date Last Browser Date Days Notes
html.elements.iframe.allow.display-capture 📋Firefox3/10/2020 Chrome9/21/2021560

2021/3

API First Browser Date Last Browser Date Days Notes
html.elements.summary.display_list_item Firefox9/20/2016 Chrome3/2/20211624

2021/1

API First Browser Date Last Browser Date Days Notes
html.elements.link.rel.preload 📋Chrome4/13/2016 Firefox1/26/20211749
Firefox: Disabled due to various web compatibility issues (e.g. bug 1405761).Firefox for Android: Disabled due to various web compatibility issues (e.g. bug 1405761).
html.elements.link.rel.preload.as-fetch Chrome4/13/2016 Firefox1/26/20211749
Firefox: Disabled due to various web compatibility issues (e.g. bug 1405761).Firefox for Android: Disabled due to various web compatibility issues (e.g. bug 1405761).
html.elements.link.rel.preload.as-font Chrome4/13/2016 Firefox1/26/20211749
Firefox: Disabled due to various web compatibility issues (e.g. bug 1405761).Firefox for Android: Disabled due to various web compatibility issues (e.g. bug 1405761).
html.elements.link.rel.preload.as-image Chrome4/13/2016 Firefox1/26/20211749
Firefox: Disabled due to various web compatibility issues (e.g. bug 1405761).Firefox for Android: Disabled due to various web compatibility issues (e.g. bug 1405761).
html.elements.link.rel.preload.as-script Chrome4/13/2016 Firefox1/26/20211749
Firefox: Disabled due to various web compatibility issues (e.g. bug 1405761).Firefox for Android: Disabled due to various web compatibility issues (e.g. bug 1405761).
html.elements.link.rel.preload.as-style Chrome4/13/2016 Firefox1/26/20211749
Firefox: Disabled due to various web compatibility issues (e.g. bug 1405761).Firefox for Android: Disabled due to various web compatibility issues (e.g. bug 1405761).
html.elements.a.implicit_noopener Firefox7/28/2020 Chrome1/19/2021175
html.elements.area.implicit_noopener Firefox7/28/2020 Chrome1/19/2021175

2020/10

API First Browser Date Last Browser Date Days Notes
html.elements.iframe.allow.web-share 📋Firefox9/22/2020 Chrome10/20/202028
Firefox: Firefox recognizes the web-share permissions policy, but this has no effect in versions of Firefox that do not support the share() method.Firefox for Android: Firefox for Android recognizes the web-share permissions policy, but this has no effect in versions of Firefox for Android that do not support the share() method.
html.elements.iframe.sandbox.allow-downloads 📋Chrome5/19/2020 Firefox10/20/2020154

2020/8

API First Browser Date Last Browser Date Days Notes
html.elements.iframe.allow.fullscreen 📋Chrome10/17/2017 Firefox8/25/20201043

2020/7

API First Browser Date Last Browser Date Days Notes
html.elements.iframe.sandbox.allow-top-navigation-by-user-activation 📋Chrome4/19/2017 Firefox7/28/20201196

2020/6

API First Browser Date Last Browser Date Days Notes
html.elements.link.imagesizes 📋Chrome3/12/2019 Firefox6/30/2020476
html.elements.link.imagesrcset 📋Chrome3/12/2019 Firefox6/30/2020476
html.elements.input.type_range.labeled_values 📋Chrome10/7/2014 Firefox6/2/20202065

2020/4

API First Browser Date Last Browser Date Days Notes
html.elements.img.loading 📋Chrome9/10/2019 Firefox4/7/2020210
html.global_attributes.nonce 📋Chrome9/5/2017 Firefox4/7/2020945
Firefox: Firefox does not prevent nonce exfiltration through content attributes.Firefox for Android: Firefox for Android does not prevent nonce exfiltration through content attributes.Safari: Safari does not prevent nonce exfiltration through content attributes.Safari on iOS: Safari on iOS does not prevent nonce exfiltration through content attributes.WebView on iOS: WebView on iOS does not prevent nonce exfiltration through content attributes.

2020/3

API First Browser Date Last Browser Date Days Notes
html.elements.audio.crossorigin 📋Chrome2/20/2014 Firefox3/10/20202210
Firefox: With crossorigin="use-credentials", cookies aren't sent during seek. See bug 1532722.Firefox for Android: With crossorigin="use-credentials", cookies aren't sent during seek. See bug 1532722.
html.elements.iframe.allow 📋Chrome7/25/2017 Firefox3/10/2020959
html.elements.iframe.allow.autoplay 📋Chrome1/23/2018 Firefox3/10/2020777
html.elements.iframe.allow.camera 📋Chrome1/23/2018 Firefox3/10/2020777
html.elements.iframe.allow.document-domain 📋Chrome1/23/2018 Firefox3/10/2020777
html.elements.iframe.allow.encrypted-media 📋Chrome1/23/2018 Firefox3/10/2020777
html.elements.iframe.allow.geolocation 📋Chrome1/23/2018 Firefox3/10/2020777
html.elements.iframe.allow.microphone 📋Chrome1/23/2018 Firefox3/10/2020777
html.elements.iframe.allow.midi 📋Chrome1/23/2018 Firefox3/10/2020777
html.elements.iframe.allow.payment 📋Chrome7/25/2017 Firefox3/10/2020959
html.elements.video.crossorigin 📋Chrome2/20/2014 Firefox3/10/20202210
Firefox: With crossorigin="use-credentials", cookies aren't sent during seek. See bug 1532722.Firefox for Android: With crossorigin="use-credentials", cookies aren't sent during seek. See bug 1532722.

2020/1

API First Browser Date Last Browser Date Days Notes
html.global_attributes.exportparts 📋Chrome3/12/2019 Firefox1/7/2020301
html.global_attributes.part 📋Chrome3/12/2019 Firefox1/7/2020301

2019/12

API First Browser Date Last Browser Date Days Notes
html.elements.img.aspect_ratio_computed_from_attributes Chrome12/10/2019 Firefox12/10/2019
Safari: Safari doesn't preserve space for images without a valid src, which may disrupt layouts that rely on lazy loading (see bug 224197).Safari on iOS: Safari on iOS doesn't preserve space for images without a valid src, which may disrupt layouts that rely on lazy loading (see bug 224197).WebView on iOS: WebView on iOS doesn't preserve space for images without a valid src, which may disrupt layouts that rely on lazy loading (see bug 224197).
html.elements.video.aspect_ratio_computed_from_attributes Chrome12/10/2019 Firefox12/10/2019

2019/5

API First Browser Date Last Browser Date Days Notes
html.elements.video.autoplay.requires_muted_audio Chrome5/29/2018 Firefox5/21/2019357
Firefox for Android: Between versions 79 and 91, the default behavior was to block videos from autoplaying, regardless of whether audio was muted.

2019/1

API First Browser Date Last Browser Date Days Notes
html.elements.marquee 📋Chrome12/11/2008 Firefox1/29/20193701
Firefox: Implements the HTMLDivElement interface.Firefox for Android: Implements the HTMLDivElement interface.
html.elements.script.referrerpolicy 📋Chrome10/16/2018 Firefox1/29/2019105

2018/10

API First Browser Date Last Browser Date Days Notes
html.elements.img.decoding 📋Chrome3/6/2018 Firefox10/23/2018231
html.elements.slot 📋Chrome8/31/2016 Firefox10/23/2018783
html.elements.slot.name Chrome8/31/2016 Firefox10/23/2018783
html.global_attributes.is 📋Chrome5/29/2018 Firefox10/23/2018147
html.global_attributes.slot 📋Chrome8/31/2016 Firefox10/23/2018783

2018/7

API First Browser Date Last Browser Date Days Notes
html.elements.iframe.sandbox.allow-orientation-lock 📋Firefox9/20/2016 Chrome7/24/2018672

2018/5

API First Browser Date Last Browser Date Days Notes
html.elements.script.nomodule 📋Chrome9/5/2017 Firefox5/9/2018246
html.elements.script.type.module Chrome9/5/2017 Firefox5/9/2018246
Chrome: Module scripts without the async attribute do not load when the page is served as XHTML (application/xhtml+xml). See bug 40518469.Chrome Android: Module scripts without the async attribute do not load when the page is served as XHTML (application/xhtml+xml). See bug 40518469.Edge: Module scripts without the async attribute do not load when the page is served as XHTML (application/xhtml+xml). See bug 40518469.Quest Browser: Module scripts without the async attribute do not load when the page is served as XHTML (application/xhtml+xml). See bug 40518469.Opera: Module scripts without the async attribute do not load when the page is served as XHTML (application/xhtml+xml). See bug 40518469.Opera Android: Module scripts without the async attribute do not load when the page is served as XHTML (application/xhtml+xml). See bug 40518469.Safari: Module scripts do not load when the page is served as XHTML (application/xhtml+xml).Safari on iOS: Module scripts do not load when the page is served as XHTML (application/xhtml+xml).Samsung Internet: Module scripts without the async attribute do not load when the page is served as XHTML (application/xhtml+xml). See bug 40518469.WebView Android: Module scripts without the async attribute do not load when the page is served as XHTML (application/xhtml+xml). See bug 40518469.WebView on iOS: Module scripts do not load when the page is served as XHTML (application/xhtml+xml).

2018/4

API First Browser Date Last Browser Date Days Notes
html.elements.select.autocomplete 📋Firefox3/13/2018 Chrome4/17/201835
html.elements.textarea.autocomplete 📋Firefox3/13/2018 Chrome4/17/201835

2018/3

API First Browser Date Last Browser Date Days Notes
html.elements.textarea.placeholder.line_breaks Chrome7/16/2014 Firefox3/13/20181336
html.elements.td.rowspan.rowspan_zero Firefox8/8/2017 Chrome3/6/2018210

2018/1

API First Browser Date Last Browser Date Days Notes
html.global_attributes.title.multi-line_titles Chrome1/23/2018 Firefox1/23/2018

2017/11

API First Browser Date Last Browser Date Days Notes
html.elements.input.type_date 📋Chrome6/26/2012 Firefox11/14/20171967
html.elements.input.type_date.disables_invalid_values_in_picker_ui Chrome6/26/2012 Firefox11/14/20171967
html.elements.input.type_time 📋Chrome6/26/2012 Firefox11/14/20171967

2017/10

API First Browser Date Last Browser Date Days Notes
html.elements.data 📋Firefox6/25/2013 Chrome10/17/20171575
html.elements.data.value 📋Firefox6/25/2013 Chrome10/17/20171575
html.elements.time 📋Firefox6/25/2013 Chrome10/17/20171575
html.elements.time.datetime Firefox6/25/2013 Chrome10/17/20171575

2017/9

API First Browser Date Last Browser Date Days Notes
html.elements.link.as 📋Chrome4/13/2016 Firefox9/28/2017533

2017/6

API First Browser Date Last Browser Date Days Notes
html.elements.meta.http-equiv.content-language 📋Firefox11/9/2004 Chrome6/5/20174591
html.elements.meta.http-equiv.content-security-policy 📋Firefox11/9/2004 Chrome6/5/20174591
html.elements.meta.http-equiv.content-type 📋Firefox11/9/2004 Chrome6/5/20174591

2017/4

API First Browser Date Last Browser Date Days Notes
html.elements.img.usemap.case_sensitive Firefox1/24/2017 Chrome4/19/201785

2017/3

API First Browser Date Last Browser Date Days Notes
html.elements.a.rel.noopener 📋Chrome3/2/2016 Firefox3/7/2017370
Firefox: Before Firefox 63, rel="noopener" created windows with all features disabled by default. Starting with Firefox 63, these windows have the same features enabled by default as any other window.Firefox for Android: Before Firefox for Android 63, rel="noopener" created windows with all features disabled by default. Starting with Firefox for Android 63, these windows have the same features enabled by default as any other window.
html.elements.area.rel.noopener 📋Chrome3/2/2016 Firefox3/7/2017370
Firefox: Before Firefox 63, rel="noopener" created windows with all features disabled by default. Starting with Firefox 63, these windows have the same features enabled by default as any other window.Firefox for Android: Before Firefox for Android 63, rel="noopener" created windows with all features disabled by default. Starting with Firefox for Android 63, these windows have the same features enabled by default as any other window.

2017/1

API First Browser Date Last Browser Date Days Notes
html.elements.input.minlength 📋Chrome1/21/2015 Firefox1/24/2017734
html.elements.textarea.minlength 📋Chrome1/21/2015 Firefox1/24/2017734

2016/11

API First Browser Date Last Browser Date Days Notes
html.elements.a.referrerpolicy 📋Chrome5/25/2016 Firefox11/15/2016174
html.elements.area.referrerpolicy 📋Chrome5/25/2016 Firefox11/15/2016174
html.elements.iframe.referrerpolicy 📋Chrome5/25/2016 Firefox11/15/2016174
html.elements.iframe.sandbox.allow-presentation 📋Chrome8/31/2016 Firefox11/15/201676
html.elements.img.referrerpolicy 📋Chrome5/25/2016 Firefox11/15/2016174
html.elements.input.webkitdirectory Chrome10/19/2010 Firefox11/15/20162219
Chrome Android: In Chrome for Android 131, choosing a directory crashes the browser (see bug 376834374).Chrome Android: Before version 131, users cannot choose a directory, only individual files (see bug 40248532.Safari on iOS: Before version 18.4, the attribute can be set but users cannot choose a directory, only individual files (see bug 271705).WebView Android: In Chrome for Android 131, choosing a directory crashes the browser (see bug 376834374).WebView Android: Before version 131, users cannot choose a directory, only individual files (see bug 40248532.WebView on iOS: Before version 18.4, the attribute can be set but users cannot choose a directory, only individual files (see bug 271705).
html.elements.link.referrerpolicy 📋Chrome5/25/2016 Firefox11/15/2016174
html.elements.track.src 📋Chrome11/6/2012 Firefox11/15/20161470
Firefox: Before Firefox 50, setting the src didn't work, though it didn't raise an error.Firefox for Android: Before Firefox for Android 50, setting the src didn't work, though it didn't raise an error.

2016/10

API First Browser Date Last Browser Date Days Notes
html.elements.area.download 📋Firefox4/2/2013 Chrome10/12/20161289

2016/9

API First Browser Date Last Browser Date Days Notes
html.elements.details 📋Chrome6/7/2011 Firefox9/20/20161932
Firefox: Before Firefox 57, there was a bug meaning that <details> elements can't be made open by default using the open attribute if they have a CSS animation active on them.Firefox for Android: There is a bug meaning that <details> elements can't be made open by default using the open attribute if they have a CSS animation active on them.
html.elements.details.open Chrome6/7/2011 Firefox9/20/20161932
html.elements.iframe.sandbox.allow-forms 📋Chrome5/25/2010 Firefox9/20/20162310
html.elements.iframe.sandbox.allow-modals 📋Chrome10/13/2015 Firefox9/20/2016343
html.elements.iframe.sandbox.allow-pointer-lock 📋Chrome11/6/2012 Firefox9/20/20161414
html.elements.iframe.sandbox.allow-popups-to-escape-sandbox 📋Chrome10/13/2015 Firefox9/20/2016343
html.elements.iframe.sandbox.allow-same-origin 📋Chrome5/25/2010 Firefox9/20/20162310
Chrome: Chrome 70 and earlier block script execution without allow-scripts, even if allow-same-origin is set. For example, any bound handlers for click events of nodes inside an iframe throw an error for blocked script execution.Chrome Android: Chrome Android 70 and earlier block script execution without allow-scripts, even if allow-same-origin is set. For example, any bound handlers for click events of nodes inside an iframe throw an error for blocked script execution.Edge: Edge 79 and earlier block script execution without allow-scripts, even if allow-same-origin is set. For example, any bound handlers for click events of nodes inside an iframe throw an error for blocked script execution.Quest Browser: Quest Browser 6.0 and earlier block script execution without allow-scripts, even if allow-same-origin is set. For example, any bound handlers for click events of nodes inside an iframe throw an error for blocked script execution.Opera: Opera 57 and earlier block script execution without allow-scripts, even if allow-same-origin is set. For example, any bound handlers for click events of nodes inside an iframe throw an error for blocked script execution.Opera Android: Opera Android 49 and earlier block script execution without allow-scripts, even if allow-same-origin is set. For example, any bound handlers for click events of nodes inside an iframe throw an error for blocked script execution.Safari: Safari blocks script execution without allow-scripts even if allow-same-origin is set. For example, any bound handlers for click events of nodes inside an iframe throw an error for blocked script execution.Safari on iOS: Safari blocks script execution without allow-scripts even if allow-same-origin is set. For example, any bound handlers for click events of nodes inside an iframe throw an error for blocked script execution.Samsung Internet: Samsung Internet 10.0 and earlier block script execution without allow-scripts, even if allow-same-origin is set. For example, any bound handlers for click events of nodes inside an iframe throw an error for blocked script execution.WebView Android: WebView Android 70 and earlier block script execution without allow-scripts, even if allow-same-origin is set. For example, any bound handlers for click events of nodes inside an iframe throw an error for blocked script execution.WebView on iOS: Safari blocks script execution without allow-scripts even if allow-same-origin is set. For example, any bound handlers for click events of nodes inside an iframe throw an error for blocked script execution.
html.elements.iframe.sandbox.allow-scripts 📋Chrome5/25/2010 Firefox9/20/20162310
html.elements.iframe.sandbox.allow-top-navigation 📋Chrome9/2/2010 Firefox9/20/20162210
html.elements.summary 📋Chrome6/7/2011 Firefox9/20/20161932

2015/12

API First Browser Date Last Browser Date Days Notes
html.elements.link.integrity 📋Chrome9/1/2015 Firefox12/15/2015105
html.elements.script.integrity 📋Chrome9/1/2015 Firefox12/15/2015105
html.elements.rtc 📋Firefox10/14/2014 Chrome12/1/2015413

2015/10

API First Browser Date Last Browser Date Days Notes
html.elements.link.rel.preconnect 📋Firefox7/2/2015 Chrome10/13/2015103
Firefox: Before Firefox 41, it doesn't obey the crossorigin attribute.Firefox for Android: Before Firefox for Android 41, it doesn't obey the crossorigin attribute.

2015/5

API First Browser Date Last Browser Date Days Notes
html.elements.img.sizes 📋Chrome10/7/2014 Firefox5/12/2015217
html.elements.img.srcset 📋Chrome4/8/2014 Firefox5/12/2015399
html.elements.picture 📋Chrome10/7/2014 Firefox5/12/2015217
html.elements.rb 📋Chrome5/25/2010 Firefox5/12/20151813
Chrome: Blink has support for parsing the rb element, but not for rendering rb content as expected.Chrome Android: Blink has support for parsing the rb element, but not for rendering rb content as expected.Edge: Blink has support for parsing the rb element, but not for rendering rb content as expected.Quest Browser: Blink has support for parsing the rb element, but not for rendering rb content as expected.Opera: Blink has support for parsing the rb element, but not for rendering rb content as expected.Opera Android: Blink has support for parsing the rb element, but not for rendering rb content as expected.Safari: Safari has support for parsing the rb element, but not for rendering rb content as expected.Safari on iOS: Safari on iOS has support for parsing the rb element, but not for rendering rb content as expected.Samsung Internet: Blink has support for parsing the rb element, but not for rendering rb content as expected.WebView Android: Blink has support for parsing the rb element, but not for rendering rb content as expected.WebView on iOS: WebView on iOS has support for parsing the rb element, but not for rendering rb content as expected.
html.elements.rp 📋Chrome5/25/2010 Firefox5/12/20151813
html.elements.rt 📋Chrome5/25/2010 Firefox5/12/20151813
Chrome: Nested <rt> elements do not render correctly due to missing display: ruby-text styling. See bug 347597919.Chrome Android: Nested <rt> elements do not render correctly due to missing display: ruby-text styling. See bug 347597919.Quest Browser: Nested <rt> elements do not render correctly due to missing display: ruby-text styling. See bug 347597919.Opera: Nested <rt> elements do not render correctly due to missing display: ruby-text styling. See bug 347597919.Opera Android: Nested <rt> elements do not render correctly due to missing display: ruby-text styling. See bug 347597919.Safari: Nested <rt> elements do not render correctly due to missing display: ruby-text styling. See bug 265316.Safari on iOS: Nested <rt> elements do not render correctly due to missing display: ruby-text styling. See bug 265316.Samsung Internet: Nested <rt> elements do not render correctly due to missing display: ruby-text styling. See bug 347597919.WebView Android: Nested <rt> elements do not render correctly due to missing display: ruby-text styling. See bug 347597919.WebView on iOS: Nested <rt> elements do not render correctly due to missing display: ruby-text styling. See bug 265316.
html.elements.ruby 📋Chrome5/25/2010 Firefox5/12/20151813
html.elements.source.sizes 📋Chrome10/7/2014 Firefox5/12/2015217
Chrome: Supports a subset of the syntax for resolution switching (using the x descriptor), but not the full syntax that can be used with sizes (using the w descriptor).Chrome Android: Supports a subset of the syntax for resolution switching (using the x descriptor), but not the full syntax that can be used with sizes (using the w descriptor).Opera: Supports a subset of the syntax for resolution switching (using the x descriptor), but not the full syntax that can be used with sizes (using the w descriptor).Opera Android: Supports a subset of the syntax for resolution switching (using the x descriptor), but not the full syntax that can be used with sizes (using the w descriptor).Samsung Internet: Supports a subset of the syntax for resolution switching (using the x descriptor), but not the full syntax that can be used with sizes (using the w descriptor).WebView Android: Supports a subset of the syntax for resolution switching (using the x descriptor), but not the full syntax that can be used with sizes (using the w descriptor).
html.elements.source.srcset 📋Chrome10/7/2014 Firefox5/12/2015217
Chrome: Supports a subset of the syntax for resolution switching (using the x descriptor), but not the full syntax that can be used with sizes (using the w descriptor).Chrome Android: Supports a subset of the syntax for resolution switching (using the x descriptor), but not the full syntax that can be used with sizes (using the w descriptor).Opera: Supports a subset of the syntax for resolution switching (using the x descriptor), but not the full syntax that can be used with sizes (using the w descriptor).Opera Android: Supports a subset of the syntax for resolution switching (using the x descriptor), but not the full syntax that can be used with sizes (using the w descriptor).Samsung Internet: Supports a subset of the syntax for resolution switching (using the x descriptor), but not the full syntax that can be used with sizes (using the w descriptor).WebView Android: Supports a subset of the syntax for resolution switching (using the x descriptor), but not the full syntax that can be used with sizes (using the w descriptor).

2015/2

API First Browser Date Last Browser Date Days Notes
html.elements.meta.name.referrer 📋Chrome2/8/2012 Firefox2/24/20151112
Chrome: Until Chrome 46, content values weren't constrained to the values listed in the spec.Chrome Android: Until Chrome Android 46, content values weren't constrained to the values listed in the spec.Firefox: The referrer value wasn't taken into account when navigation was happening via the context menu or middle click until Firefox 39.Firefox for Android: The referrer value wasn't taken into account when navigation was happening via the context menu or middle click until Firefox for Android 39.Internet Explorer: Browsers initially supported an early draft of the specification which can only use a meta tag and is only compatible with the origin value from the new spec.Quest Browser: Until Quest Browser 5.0, content values weren't constrained to the values listed in the spec.Opera: Until Opera 33, content values weren't constrained to the values listed in the spec.Opera Android: Until Opera Android 33, content values weren't constrained to the values listed in the spec.Samsung Internet: Until Samsung Internet 5.0, content values weren't constrained to the values listed in the spec.WebView Android: Until WebView Android 46, content values weren't constrained to the values listed in the spec.

2015/1

API First Browser Date Last Browser Date Days Notes
html.elements.body.bottommargin Chrome12/11/2008 Firefox1/13/20152224
Firefox: Before Firefox 35, it was supported in Quirks Mode only.Firefox for Android: Before Firefox for Android 35, it was supported in Quirks Mode only.
html.elements.body.leftmargin Chrome12/11/2008 Firefox1/13/20152224
Firefox: Before Firefox 35, it was supported in Quirks Mode only.Firefox for Android: Before Firefox for Android 35, it was supported in Quirks Mode only.
html.elements.body.rightmargin Chrome12/11/2008 Firefox1/13/20152224
Firefox: Before Firefox 35, it was supported in Quirks Mode only.Firefox for Android: Before Firefox for Android 35, it was supported in Quirks Mode only.
html.elements.body.topmargin Chrome12/11/2008 Firefox1/13/20152224
Firefox: Before Firefox 35, it was supported in Quirks Mode only.Firefox for Android: Before Firefox for Android 35, it was supported in Quirks Mode only.

2014/10

API First Browser Date Last Browser Date Days Notes
html.elements.a.rel.noreferrer 📋Chrome12/13/2011 Firefox10/14/20141036
Internet Explorer: Only supported in IE11 in later versions of Windows 10 (creators update). (Per caniuse.com.)
html.elements.area.rel.noreferrer 📋Chrome12/13/2011 Firefox10/14/20141036
Internet Explorer: Only supported in IE11 in later versions of Windows 10 (creators update). (Per caniuse.com.)
html.elements.iframe.allowfullscreen 📋Firefox1/8/2013 Chrome10/7/2014637
Safari on iOS: Only available on iPad, not on iPhone.Safari on iOS: Shows an overlay button which can not be disabled. Swiping down exits fullscreen mode, making it unsuitable for some use cases like games.WebView on iOS: Only available on iPad, not on iPhone.WebView on iOS: Shows an overlay button which can not be disabled. Swiping down exits fullscreen mode, making it unsuitable for some use cases like games.

2014/9

API First Browser Date Last Browser Date Days Notes
html.global_attributes.id 📋Chrome12/11/2008 Firefox9/2/20142091
Firefox: id is a true global attribute only since Firefox 32.Firefox for Android: id is a true global attribute only since Firefox for Android 32.

2014/7

API First Browser Date Last Browser Date Days Notes
html.elements.link.sizes 📋Chrome10/25/2011 Firefox7/22/20141001
html.elements.track 📋Chrome11/6/2012 Firefox7/22/2014623
Chrome Android: Doesn't work for fullscreen video.Quest Browser: Doesn't work for fullscreen video.Samsung Internet: Doesn't work for fullscreen video.WebView Android: Doesn't work for fullscreen video.
html.elements.track.default 📋Chrome11/6/2012 Firefox7/22/2014623
html.elements.track.kind 📋Chrome11/6/2012 Firefox7/22/2014623
html.elements.track.label 📋Chrome11/6/2012 Firefox7/22/2014623
html.elements.track.srclang 📋Chrome11/6/2012 Firefox7/22/2014623

2014/6

API First Browser Date Last Browser Date Days Notes
html.elements.area.rel 📋Chrome12/13/2011 Firefox6/10/2014910

2014/4

API First Browser Date Last Browser Date Days Notes
html.elements.input.type_color 📋Chrome6/26/2012 Firefox4/29/2014672
Firefox for Android: Firefox for Android doesn't allow the user to choose a custom color, only one of the predefined ones.
html.elements.input.type_number 📋Chrome10/19/2010 Firefox4/29/20141288
Chrome: Prevents users from typing non-numeric content.Chrome Android: Prevents users from typing non-numeric content.Firefox: Allows users to type non-numeric content, with the value reflecting an empty string.Firefox for Android: Allows users to type non-numeric content, with the value reflecting an empty string.Quest Browser: Prevents users from typing non-numeric content.Opera: Prevents users from typing non-numeric content.Opera Android: Prevents users from typing non-numeric content.Safari: Allows users to type non-numeric content, with the value reflecting an empty string.Safari on iOS: Allows users to type non-numeric content, with the value reflecting an empty string.Samsung Internet: Prevents users from typing non-numeric content.WebView Android: Prevents users from typing non-numeric content.WebView on iOS: Allows users to type non-numeric content, with the value reflecting an empty string.
html.elements.input.type_number.list 📋Chrome9/25/2012 Firefox4/29/2014581
html.elements.link.crossorigin 📋Firefox1/8/2013 Chrome4/8/2014455
Firefox: Before Firefox 83, crossorigin is not supported for rel="icon".Firefox for Android: Before Firefox for Android 83, crossorigin is not supported for rel="icon".

2014/3

API First Browser Date Last Browser Date Days Notes
html.elements.iframe.sandbox.allow-popups 📋Chrome2/8/2012 Firefox3/18/2014769

2014/2

API First Browser Date Last Browser Date Days Notes
html.elements.hr.color Firefox11/9/2004 Chrome2/20/20143390

2013/10

API First Browser Date Last Browser Date Days Notes
html.elements.iframe.srcdoc 📋Chrome6/26/2012 Firefox10/29/2013490
html.elements.video.muted 📋Firefox3/13/2012 Chrome10/1/2013567

2013/8

API First Browser Date Last Browser Date Days Notes
html.elements.input.type_range 📋Chrome1/25/2010 Firefox8/6/20131289
WebView Android: Pre-Chromium Android WebView recognizes the range type, but doesn't implement a range-specific control.

2013/6

API First Browser Date Last Browser Date Days Notes
html.elements.template 📋Chrome3/26/2013 Firefox6/25/201391

2013/5

API First Browser Date Last Browser Date Days Notes
html.elements.main 📋Chrome3/26/2013 Firefox5/14/201349

2013/4

API First Browser Date Last Browser Date Days Notes
html.elements.a.download 📋Chrome9/16/2011 Firefox4/2/2013564
Chrome: Starting in Chrome 65, cross-origin downloads are not supported on the <a> element.Chrome Android: Starting in Chrome Android 65, cross-origin downloads are not supported on the <a> element.Edge: Starting in Edge 79, cross-origin downloads are not supported on the <a> element.Edge: Until Edge 14 (build 14357), attempting to download data URIs caused Edge to crash (bug 7160092).Edge: Edge 17 or older didn't follow the attributes' value to determine filename (bug 7260192).Firefox for Android: The attribute's filename value only affects the suggested file name for the blob: and data: URI schemes. Other schemes ignore the suggested filename. See bug 1845642.Quest Browser: Starting in Quest Browser 5.0, cross-origin downloads are not supported on the <a> element.Opera: Starting in Opera 52, cross-origin downloads are not supported on the <a> element.Opera Android: Starting in Opera Android 47, cross-origin downloads are not supported on the <a> element.Samsung Internet: Starting in Samsung Internet 9.0, cross-origin downloads are not supported on the <a> element.WebView Android: Starting in WebView Android 65, cross-origin downloads are not supported on the <a> element.

2013/1

API First Browser Date Last Browser Date Days Notes
html.elements.ol.reversed 📋Chrome3/28/2012 Firefox1/8/2013286

2012/11

API First Browser Date Last Browser Date Days Notes
html.elements.iframe.sandbox 📋Chrome5/25/2010 Firefox11/20/2012910

2012/10

API First Browser Date Last Browser Date Days Notes
html.elements.input.max 📋Chrome1/25/2010 Firefox10/9/2012988
html.elements.input.min 📋Chrome1/25/2010 Firefox10/9/2012988
html.elements.input.step 📋Chrome5/25/2010 Firefox10/9/2012868
html.elements.meter 📋Chrome9/2/2010 Firefox10/9/2012768
html.elements.meter.high 📋Chrome9/2/2010 Firefox10/9/2012768
html.elements.meter.low 📋Chrome9/2/2010 Firefox10/9/2012768
html.elements.meter.max 📋Chrome9/2/2010 Firefox10/9/2012768
html.elements.meter.min 📋Chrome9/2/2010 Firefox10/9/2012768
html.elements.meter.optimum 📋Chrome9/2/2010 Firefox10/9/2012768
html.elements.meter.value 📋Chrome9/2/2010 Firefox10/9/2012768

2012/9

API First Browser Date Last Browser Date Days Notes
html.elements.datalist.input_type_email 📋Firefox3/22/2011 Chrome9/25/2012553
html.elements.datalist.input_type_number 📋Firefox3/22/2011 Chrome9/25/2012553
html.elements.datalist.input_type_search 📋Firefox3/22/2011 Chrome9/25/2012553
html.elements.datalist.input_type_tel 📋Firefox3/22/2011 Chrome9/25/2012553
html.elements.datalist.input_type_url 📋Firefox3/22/2011 Chrome9/25/2012553
html.elements.input.type_email.list 📋Firefox3/22/2011 Chrome9/25/2012553
html.elements.input.type_search.list 📋Firefox3/22/2011 Chrome9/25/2012553
html.elements.input.type_tel.list 📋Firefox3/22/2011 Chrome9/25/2012553
html.elements.input.type_url.list 📋Firefox3/22/2011 Chrome9/25/2012553

2012/8

API First Browser Date Last Browser Date Days Notes
html.elements.source.media 📋Chrome9/15/2009 Firefox8/28/20121078
Firefox: media is supported in <source> within <picture>, <audio>, and <video>. In Firefox 53-119, media is supported only in <source> within <picture>.Firefox for Android: media is supported in <source> within <picture>, <audio>, and <video>. In Firefox for Android 53-119, media is supported only in <source> within <picture>.

2012/7

API First Browser Date Last Browser Date Days Notes
html.elements.script.crossorigin 📋Chrome5/15/2012 Firefox7/17/201263
Safari: The crossorigin attribute was implemented in WebKit in WebKit bug 81438.Safari on iOS: The crossorigin attribute was implemented in WebKit in WebKit bug 81438.WebView on iOS: The crossorigin attribute was implemented in WebKit in WebKit bug 81438.

2012/6

API First Browser Date Last Browser Date Days Notes
html.elements.datalist 📋Firefox3/22/2011 Chrome6/26/2012462
Firefox for Android: The dropdown menu containing available options does not appear. See bug 1535985.
html.elements.datalist.input_type_text 📋Firefox3/22/2011 Chrome6/26/2012462
html.elements.fieldset.disabled 📋Firefox3/22/2011 Chrome6/26/2012462
Edge: Does not work with nested fieldsets. For example: <fieldset disabled><fieldset><!--Still enabled--></fieldset></fieldset>Internet Explorer: Not all form control descendants of a disabled fieldset are properly disabled in IE11; see IE bug 817488: input[type='file'] not disabled inside disabled fieldset and IE bug 962368: Can still edit input[type='text'] within fieldset[disabled].
html.elements.input.type_text.list 📋Firefox3/22/2011 Chrome6/26/2012462

2012/5

API First Browser Date Last Browser Date Days Notes
html.elements.fieldset.name 📋Firefox3/22/2011 Chrome5/15/2012420

2012/3

API First Browser Date Last Browser Date Days Notes
html.elements.audio.loop 📋Chrome9/15/2009 Firefox3/13/2012910
html.elements.audio.muted 📋Chrome10/25/2011 Firefox3/13/2012140
html.elements.video.loop 📋Chrome9/15/2009 Firefox3/13/2012910

2012/1

API First Browser Date Last Browser Date Days Notes
html.elements.a.href.href_top Chrome12/11/2008 Firefox1/31/20121146
html.elements.bdi 📋Chrome12/13/2011 Firefox1/31/201249
html.elements.bdo 📋Chrome10/25/2011 Firefox1/31/201298

2011/12

API First Browser Date Last Browser Date Days Notes
html.elements.textarea.wrap 📋Firefox3/22/2011 Chrome12/13/2011266

2011/11

API First Browser Date Last Browser Date Days Notes
html.elements.img.crossorigin 📋Chrome8/2/2011 Firefox11/8/201198

2011/10

API First Browser Date Last Browser Date Days Notes
html.elements.dfn 📋Firefox11/9/2004 Chrome10/25/20112541

2011/9

API First Browser Date Last Browser Date Days Notes
html.elements.form.autocomplete 📋Firefox3/22/2011 Chrome9/16/2011178
Chrome: The Google Chrome UI for auto-complete request varies, depending on whether autocomplete is set to off on <input> elements as well as their form. Specifically, when a form has autocomplete set to off and its <input> element's autocomplete attribute is not set, then if the user asks for autofill suggestions for the <input> element, Chrome might display a message saying 'autocomplete has been disabled for this form.' On the other hand, if both the form and the input element have autocomplete set to off, the browser will not display that message. For this reason, you should set autocomplete to off for each <input> that has custom auto-completion.Chrome Android: The Chrome Android UI for auto-complete request varies, depending on whether autocomplete is set to off on <input> elements as well as their form. Specifically, when a form has autocomplete set to off and its <input> element's autocomplete attribute is not set, then if the user asks for autofill suggestions for the <input> element, Chrome Android might display a message saying 'autocomplete has been disabled for this form.' On the other hand, if both the form and the input element have autocomplete set to off, the browser will not display that message. For this reason, you should set autocomplete to off for each <input> that has custom auto-completion.Quest Browser: The Quest Browser UI for auto-complete request varies, depending on whether autocomplete is set to off on <input> elements as well as their form. Specifically, when a form has autocomplete set to off and its <input> element's autocomplete attribute is not set, then if the user asks for autofill suggestions for the <input> element, Quest Browser might display a message saying 'autocomplete has been disabled for this form.' On the other hand, if both the form and the input element have autocomplete set to off, the browser will not display that message. For this reason, you should set autocomplete to off for each <input> that has custom auto-completion.Opera: The Opera UI for auto-complete request varies, depending on whether autocomplete is set to off on <input> elements as well as their form. Specifically, when a form has autocomplete set to off and its <input> element's autocomplete attribute is not set, then if the user asks for autofill suggestions for the <input> element, Opera might display a message saying 'autocomplete has been disabled for this form.' On the other hand, if both the form and the input element have autocomplete set to off, the browser will not display that message. For this reason, you should set autocomplete to off for each <input> that has custom auto-completion.Opera Android: The Opera Android UI for auto-complete request varies, depending on whether autocomplete is set to off on <input> elements as well as their form. Specifically, when a form has autocomplete set to off and its <input> element's autocomplete attribute is not set, then if the user asks for autofill suggestions for the <input> element, Opera Android might display a message saying 'autocomplete has been disabled for this form.' On the other hand, if both the form and the input element have autocomplete set to off, the browser will not display that message. For this reason, you should set autocomplete to off for each <input> that has custom auto-completion.Samsung Internet: The Samsung Internet UI for auto-complete request varies, depending on whether autocomplete is set to off on <input> elements as well as their form. Specifically, when a form has autocomplete set to off and its <input> element's autocomplete attribute is not set, then if the user asks for autofill suggestions for the <input> element, Samsung Internet might display a message saying 'autocomplete has been disabled for this form.' On the other hand, if both the form and the input element have autocomplete set to off, the browser will not display that message. For this reason, you should set autocomplete to off for each <input> that has custom auto-completion.WebView Android: The WebView Android UI for auto-complete request varies, depending on whether autocomplete is set to off on <input> elements as well as their form. Specifically, when a form has autocomplete set to off and its <input> element's autocomplete attribute is not set, then if the user asks for autofill suggestions for the <input> element, WebView Android might display a message saying 'autocomplete has been disabled for this form.' On the other hand, if both the form and the input element have autocomplete set to off, the browser will not display that message. For this reason, you should set autocomplete to off for each <input> that has custom auto-completion.
html.elements.input.autocomplete 📋Firefox3/22/2011 Chrome9/16/2011178

2011/8

API First Browser Date Last Browser Date Days Notes
html.elements.progress 📋Chrome9/2/2010 Firefox8/16/2011348
Firefox: Before Firefox 14, the <progress> element was incorrectly classified as a form element, and therefore had a form attribute. This has been fixed.Firefox: Firefox provides the ::-moz-progress-bar pseudo-element, which lets you style the part of the interior of the progress bar representing the amount of work completed so far.Firefox for Android: Before Firefox for Android 14, the <progress> element was incorrectly classified as a form element, and therefore had a form attribute. This has been fixed.Firefox for Android: Firefox for Android provides the ::-moz-progress-bar pseudo-element, which lets you style the part of the interior of the progress bar representing the amount of work completed so far.Safari on iOS: Safari on iOS does not support indeterminate progress bars (they are rendered like 0%-completed progress bars).WebView on iOS: WebView on iOS does not support indeterminate progress bars (they are rendered like 0%-completed progress bars).
html.elements.progress.max 📋Chrome9/2/2010 Firefox8/16/2011348
html.elements.progress.value 📋Chrome9/2/2010 Firefox8/16/2011348
html.global_attributes.data_attributes 📋Chrome10/19/2010 Firefox8/16/2011301

2011/6

API First Browser Date Last Browser Date Days Notes
html.elements.a.ping 📋Firefox11/9/2004 Chrome6/7/20112401
Firefox: This property is exposed but has no effect if the browser.send_pings preference is not set to true. See bug 951104.Firefox for Android: This property is exposed but has no effect if the browser.send_pings preference is not set to true. See bug 951104.
html.elements.area.ping 📋Firefox11/9/2004 Chrome6/7/20112401
Firefox: This property is exposed but has no effect if the browser.send_pings preference is not set to true. See bug 951104.Firefox for Android: This property is exposed but has no effect if the browser.send_pings preference is not set to true. See bug 951104.

2011/3

API First Browser Date Last Browser Date Days Notes
html.elements.article 📋Chrome5/25/2010 Firefox3/22/2011301
html.elements.aside 📋Chrome5/25/2010 Firefox3/22/2011301
html.elements.audio.preload 📋Chrome9/15/2009 Firefox3/22/2011553
Chrome: Defaults to metadata in Chrome 64.Chrome Android: Defaults to metadata in Chrome Android 64.Quest Browser: Defaults to metadata in Quest Browser 5.0.Opera: Defaults to metadata in Opera 51.Opera Android: Defaults to metadata in Opera 51.Samsung Internet: Defaults to metadata in Samsung Internet 9.0.WebView Android: Defaults to metadata in Chrome 64.
html.elements.base.href.relative_url Chrome12/11/2008 Firefox3/22/2011831
html.elements.button.form Chrome2/3/2011 Firefox3/22/201147
html.elements.button.formaction Chrome2/3/2011 Firefox3/22/201147
html.elements.button.formenctype Chrome2/3/2011 Firefox3/22/201147
html.elements.button.formmethod Chrome2/3/2011 Firefox3/22/201147
html.elements.button.formnovalidate Chrome2/3/2011 Firefox3/22/201147
html.elements.button.formtarget Chrome2/3/2011 Firefox3/22/201147
html.elements.figcaption 📋Chrome12/2/2010 Firefox3/22/2011110
html.elements.figure 📋Chrome12/2/2010 Firefox3/22/2011110
html.elements.footer 📋Chrome5/25/2010 Firefox3/22/2011301
html.elements.form.novalidate 📋Chrome3/8/2011 Firefox3/22/201114
html.elements.header 📋Chrome5/25/2010 Firefox3/22/2011301
html.elements.hgroup 📋Chrome5/25/2010 Firefox3/22/2011301
html.elements.input.formaction 📋Chrome2/3/2011 Firefox3/22/201147
html.elements.input.formenctype 📋Chrome2/3/2011 Firefox3/22/201147
html.elements.input.formmethod 📋Chrome2/3/2011 Firefox3/22/201147
html.elements.input.formnovalidate 📋Chrome1/25/2010 Firefox3/22/2011421
html.elements.input.formtarget 📋Chrome2/3/2011 Firefox3/22/201147
html.elements.input.pattern 📋Chrome1/25/2010 Firefox3/22/2011421
html.elements.input.placeholder 📋Chrome9/15/2009 Firefox3/22/2011553
html.elements.input.required 📋Chrome1/25/2010 Firefox3/22/2011421
html.elements.input.type_search 📋Chrome5/25/2010 Firefox3/22/2011301
html.elements.input.type_tel 📋Chrome9/15/2009 Firefox3/22/2011553
Chrome: The field type doesn't demonstrate any special behavior.Safari: The field type doesn't demonstrate any special behavior.
html.elements.mark 📋Chrome10/19/2010 Firefox3/22/2011154
html.elements.nav 📋Chrome5/25/2010 Firefox3/22/2011301
html.elements.output 📋Chrome3/8/2011 Firefox3/22/201114
html.elements.output.for 📋Chrome3/8/2011 Firefox3/22/201114
html.elements.output.form 📋Chrome3/8/2011 Firefox3/22/201114
html.elements.output.name 📋Chrome3/8/2011 Firefox3/22/201114
html.elements.plaintext 📋Chrome12/11/2008 Firefox3/22/2011831
Firefox: Before Firefox 4, this element implemented the HTMLSpanElement interface instead of the standard HTMLElement interface.
html.elements.section 📋Chrome5/25/2010 Firefox3/22/2011301
html.elements.select.required 📋Chrome3/8/2011 Firefox3/22/201114
html.elements.textarea.maxlength 📋Chrome1/25/2010 Firefox3/22/2011421
Safari: Before Safari 17, newline characters counted as two characters instead of one. See bug 249916.Safari on iOS: Before Safari on iOS 17, newline characters counted as two characters instead of one. See bug 249916.WebView on iOS: Before WebView on iOS 17, newline characters counted as two characters instead of one. See bug 249916.
html.elements.textarea.placeholder 📋Chrome1/25/2010 Firefox3/22/2011421
html.elements.textarea.required 📋Chrome1/25/2010 Firefox3/22/2011421
html.elements.video.preload 📋Chrome9/15/2009 Firefox3/22/2011553
Chrome: Defaults to metadata in Chrome 64.Chrome Android: Defaults to metadata in Chrome Android 64.Quest Browser: Defaults to metadata in Quest Browser 5.0.Opera: Defaults to metadata in Opera 51.Opera Android: Defaults to metadata in Opera Android 47.Samsung Internet: Defaults to metadata in Samsung Internet 9.0.WebView Android: Defaults to metadata in WebView Android 64.
html.global_attributes.hidden 📋Chrome3/8/2011 Firefox3/22/201114
Safari: This attribute has no effect on <option> elements.Safari on iOS: This attribute has no effect on <option> elements.WebView on iOS: This attribute has no effect on <option> elements.

2011/2

API First Browser Date Last Browser Date Days Notes
html.global_attributes.spellcheck 📋Firefox10/24/2006 Chrome2/3/20111563
Chrome Android: Only supported on <textarea>.Firefox for Android: Only supported on <textarea>.Opera Android: Only supported on <textarea>.Safari on iOS: Only supported on <textarea>.Samsung Internet: Only supported on <textarea>.WebView Android: Only supported on <textarea>.WebView on iOS: Only supported on <textarea>.

2010/12

API First Browser Date Last Browser Date Days Notes
html.elements.link.rel.prefetch 📋Firefox10/24/2006 Chrome12/2/20101500
Chrome: Requires secure contextChrome Android: Requires secure contextEdge: Requires secure contextFirefox: Requires secure contextFirefox for Android: Requires secure contextQuest Browser: Requires secure contextOpera: Requires secure contextOpera Android: Requires secure contextSamsung Internet: Requires secure contextWebView Android: Requires secure context

2010/5

API First Browser Date Last Browser Date Days Notes
html.elements.input.type_email 📋Firefox11/9/2004 Chrome5/25/20102023
Safari on iOS: Doesn't do validation, but instead offers a custom 'email' keyboard, which is designed to make entering email addresses easier.Safari on iOS: The custom 'email' keyboard does not provide a comma key, so users cannot enter multiple email addresses.Safari on iOS: Automatically applies a default style of opacity: 0.4 to disable textual <input> elements, including those of type 'email'. Other major browsers don't currently share this particular default style.WebView on iOS: Doesn't do validation, but instead offers a custom 'email' keyboard, which is designed to make entering email addresses easier.WebView on iOS: The custom 'email' keyboard does not provide a comma key, so users cannot enter multiple email addresses.WebView on iOS: Automatically applies a default style of opacity: 0.4 to disable textual <input> elements, including those of type 'email'. Other major browsers don't currently share this particular default style.

2010/1

API First Browser Date Last Browser Date Days Notes
html.elements.link.rel.icon Firefox10/24/2006 Chrome1/25/20101189
Chrome: If both ICO and PNG are available, will use ICO over PNG if ICO has better matching sizes set. (Per caniuse.com.).Edge: In version 79 and later (Blink-based Edge), if both ICO and PNG are available, will use ICO over PNG if ICO has better matching sizes set. (Per caniuse.com.)Firefox: Before Firefox 83, the crossorigin attribute is not supported for rel="icon".Firefox: The media attribute is not supported for rel="icon", see bug 1603885.Opera: In version 15 and later (Blink-based Opera), if both ICO and PNG are available, will use ICO over PNG if ICO has better matching sizes set. (Per caniuse.com.)Safari: If both ICO and PNG are available, will ALWAYS use ICO file, regardless of sizes set. (Per caniuse.com.)Safari on iOS: Does not use favicons at all (but may have alternative for bookmarks, etc.). (Per caniuse.com.)WebView on iOS: Does not use favicons at all (but may have alternative for bookmarks, etc.). (Per caniuse.com.)
html.global_attributes.draggable 📋Firefox10/24/2006 Chrome1/25/20101189
html.elements.input.multiple 📋Chrome5/21/2009 Firefox1/21/2010245
html.elements.script.async 📋Chrome12/11/2008 Firefox1/21/2010406
html.elements.video.poster 📋Chrome9/15/2009 Firefox1/21/2010128

2009/9

API First Browser Date Last Browser Date Days Notes
html.elements.audio 📋Firefox6/30/2009 Chrome9/15/200977
Firefox: For Firefox to play audio, the server must serve the file using the correct MIME type.Firefox for Android: For Firefox for Android to play audio, the server must serve the file using the correct MIME type.
html.elements.audio.controls 📋Firefox6/30/2009 Chrome9/15/200977
html.elements.audio.src 📋Firefox6/30/2009 Chrome9/15/200977
html.elements.source 📋Firefox6/30/2009 Chrome9/15/200977
Firefox: Until Firefox 15, Firefox picked the first source element that has a type matching the MIME-type of a supported media format; see bug 449363 for details.Firefox for Android: Until Firefox for Android 15, Firefox for Android picked the first source element that has a type matching the MIME-type of a supported media format; see bug 449363 for details.
html.elements.source.src 📋Firefox6/30/2009 Chrome9/15/200977
html.elements.source.type 📋Firefox6/30/2009 Chrome9/15/200977
html.elements.video 📋Firefox6/30/2009 Chrome9/15/200977
html.elements.video.autoplay 📋Firefox6/30/2009 Chrome9/15/200977
html.elements.video.controls 📋Firefox6/30/2009 Chrome9/15/200977
html.elements.video.height 📋Firefox6/30/2009 Chrome9/15/200977
html.elements.video.src 📋Firefox6/30/2009 Chrome9/15/200977
html.elements.video.width 📋Firefox6/30/2009 Chrome9/15/200977

2009/6

API First Browser Date Last Browser Date Days Notes
html.elements.script.defer 📋Chrome12/11/2008 Firefox6/30/2009201
Chrome: Chrome does not defer scripts with the defer attribute when the page is served as XHTML (application/xhtml+xml), see bug 41253514 and bug 41408348Chrome Android: Chrome Android does not defer scripts with the defer attribute when the page is served as XHTML (application/xhtml+xml), see bug 41253514 and bug 41408348Firefox: Since Firefox 3.6, the defer attribute is ignored on scripts that don't have the src attribute. However, in Firefox 3.5 even inline scripts are deferred if the defer attribute is set.Internet Explorer: Before version 10, Internet Explorer implemented defer by a proprietary specification. Since version 10 it conforms to the W3C specification.Quest Browser: Quest Browser does not defer scripts with the defer attribute when the page is served as XHTML (application/xhtml+xml), see bug 41253514 and bug 41408348Opera: Opera does not defer scripts with the defer attribute when the page is served as XHTML (application/xhtml+xml), see bug 41253514 and bug 41408348Opera Android: Opera Android does not defer scripts with the defer attribute when the page is served as XHTML (application/xhtml+xml), see bug 41253514 and bug 41408348Samsung Internet: Samsung Internet does not defer scripts with the defer attribute when the page is served as XHTML (application/xhtml+xml), see bug 41253514 and bug 41408348WebView Android: WebView Android does not defer scripts with the defer attribute when the page is served as XHTML (application/xhtml+xml), see bug 41253514 and bug 41408348

2009/5

API First Browser Date Last Browser Date Days Notes
html.elements.abbr 📋Firefox11/9/2004 Chrome5/21/20091654
Firefox: Before Firefox 4, this element implemented the HTMLSpanElement interface instead of the standard HTMLElement interface.

2008/12

API First Browser Date Last Browser Date Days Notes
html.elements.a 📋Firefox11/9/2004 Chrome12/11/20081493
Firefox: Starting with Firefox 41, <a> without href attribute is no longer classified as interactive content: clicking it inside <label> will activate labelled content (bug 1167816).Firefox for Android: Starting with Firefox for Android 41, <a> without href attribute is no longer classified as interactive content: clicking it inside <label> will activate labelled content (bug 1167816).
html.elements.a.charset 📋Firefox11/9/2004 Chrome12/11/20081493
html.elements.a.href 📋Firefox11/9/2004 Chrome12/11/20081493
html.elements.a.hreflang 📋Firefox11/9/2004 Chrome12/11/20081493
html.elements.a.name 📋Firefox11/9/2004 Chrome12/11/20081493
html.elements.a.rel 📋Firefox11/9/2004 Chrome12/11/20081493
html.elements.a.rev 📋Firefox11/9/2004 Chrome12/11/20081493
html.elements.a.target 📋Firefox11/9/2004 Chrome12/11/20081493
html.elements.a.type 📋Firefox11/9/2004 Chrome12/11/20081493
html.elements.acronym 📋Firefox11/9/2004 Chrome12/11/20081493
html.elements.address 📋Firefox11/9/2004 Chrome12/11/20081493
html.elements.area 📋Firefox11/9/2004 Chrome12/11/20081493
html.elements.area.alt 📋Firefox11/9/2004 Chrome12/11/20081493
html.elements.area.coords 📋Firefox11/9/2004 Chrome12/11/20081493
html.elements.area.href 📋Firefox11/9/2004 Chrome12/11/20081493
html.elements.area.nohref 📋Firefox11/9/2004 Chrome12/11/20081493
html.elements.area.shape 📋Firefox11/9/2004 Chrome12/11/20081493
html.elements.area.target 📋Firefox11/9/2004 Chrome12/11/20081493
html.elements.b 📋Firefox11/9/2004 Chrome12/11/20081493
Firefox: Before Firefox 4, this element implemented the HTMLSpanElement interface instead of the standard HTMLElement interface.
html.elements.base 📋Firefox11/9/2004 Chrome12/11/20081493
Internet Explorer: Before Internet Explorer 7, <base> can be positioned anywhere in the document and the nearest value of <base> is used.
html.elements.base.href 📋Firefox11/9/2004 Chrome12/11/20081493
html.elements.base.target 📋Firefox11/9/2004 Chrome12/11/20081493
html.elements.big 📋Firefox11/9/2004 Chrome12/11/20081493
html.elements.blockquote 📋Firefox11/9/2004 Chrome12/11/20081493
html.elements.blockquote.cite Firefox11/9/2004 Chrome12/11/20081493
html.elements.body 📋Firefox11/9/2004 Chrome12/11/20081493
html.elements.body.alink Firefox11/9/2004 Chrome12/11/20081493
html.elements.body.background Firefox11/9/2004 Chrome12/11/20081493
html.elements.body.bgcolor Firefox11/9/2004 Chrome12/11/20081493
html.elements.body.link Firefox11/9/2004 Chrome12/11/20081493
html.elements.body.text Firefox11/9/2004 Chrome12/11/20081493
html.elements.body.vlink Firefox11/9/2004 Chrome12/11/20081493
html.elements.br 📋Firefox11/9/2004 Chrome12/11/20081493
html.elements.br.clear Firefox11/9/2004 Chrome12/11/20081493
html.elements.button 📋Firefox11/9/2004 Chrome12/11/20081493
html.elements.button.disabled 📋Firefox11/9/2004 Chrome12/11/20081493
html.elements.button.name Firefox11/9/2004 Chrome12/11/20081493
html.elements.button.type Firefox11/9/2004 Chrome12/11/20081493
html.elements.button.value Firefox11/9/2004 Chrome12/11/20081493
html.elements.canvas 📋Firefox11/29/2005 Chrome12/11/20081108
Firefox: Before Firefox 5, the canvas width and height were signed integers instead of unsigned integers.Firefox: Before Firefox 6, a <canvas> element with a zero width or height would be rendered as if it had default dimensions.Firefox: Before Firefox 12, if JavaScript is disabled, the <canvas> element was being rendered instead of showing the fallback content as per the specification. Since then, the fallback content is rendered instead.Firefox for Android: Before Firefox for Android 5, the canvas width and height were signed integers instead of unsigned integers.Firefox for Android: Before Firefox for Android 6, a <canvas> element with a zero width or height would be rendered as if it had default dimensions.Firefox for Android: Before Firefox for Android 14, if JavaScript is disabled, the <canvas> element was being rendered instead of showing the fallback content as per the specification. Since then, the fallback content is rendered instead.Safari: Although early versions of Apple's Safari browser don't require the closing tag, the specification indicates that it is required, so you should be sure to include it for broadest compatibility. Before version 2, Safari will render the content of the fallback in addition to the canvas itself unless you use CSS tricks to mask it.
html.elements.canvas.height 📋Firefox11/29/2005 Chrome12/11/20081108
Firefox: Before Firefox 5, the canvas width and height were signed integers instead of unsigned integers.Firefox: Before Firefox 6, a <canvas> element with a zero width or height would be rendered as if it had default dimensions.Firefox: Before Firefox 12, if JavaScript is disabled, the <canvas> element was being rendered instead of showing the fallback content as per the specification. Since then, the fallback content is rendered instead.Firefox for Android: Before Firefox for Android 5, the canvas width and height were signed integers instead of unsigned integers.Firefox for Android: Before Firefox for Android 6, a <canvas> element with a zero width or height would be rendered as if it had default dimensions.Firefox for Android: Before Firefox for Android 14, if JavaScript is disabled, the <canvas> element was being rendered instead of showing the fallback content as per the specification. Since then, the fallback content is rendered instead.Safari: Although early versions of Apple's Safari browser don't require the closing tag, the specification indicates that it is required, so you should be sure to include it for broadest compatibility. Before version 2, Safari will render the content of the fallback in addition to the canvas itself unless you use CSS tricks to mask it.
html.elements.canvas.width 📋Firefox11/29/2005 Chrome12/11/20081108
Firefox: Before Firefox 5, the canvas width and height were signed integers instead of unsigned integers.Firefox: Before Firefox 6, a <canvas> element with a zero width or height would be rendered as if it had default dimensions.Firefox: Before Firefox 12, if JavaScript is disabled, the <canvas> element was being rendered instead of showing the fallback content as per the specification. Since then, the fallback content is rendered instead.Firefox for Android: Before Firefox for Android 5, the canvas width and height were signed integers instead of unsigned integers.Firefox for Android: Before Firefox for Android 6, a <canvas> element with a zero width or height would be rendered as if it had default dimensions.Firefox for Android: Before Firefox for Android 14, if JavaScript is disabled, the <canvas> element was being rendered instead of showing the fallback content as per the specification. Since then, the fallback content is rendered instead.Safari: Although early versions of Apple's Safari browser don't require the closing tag, the specification indicates that it is required, so you should be sure to include it for broadest compatibility. Before version 2, Safari will render the content of the fallback in addition to the canvas itself unless you use CSS tricks to mask it.
html.elements.caption 📋Firefox11/9/2004 Chrome12/11/20081493
html.elements.caption.align Firefox11/9/2004 Chrome12/11/20081493
html.elements.center 📋Firefox11/9/2004 Chrome12/11/20081493
Firefox: Before Firefox 4, this element implemented the HTMLSpanElement interface instead of the standard HTMLElement interface.Firefox for Android: Before Firefox for Android 4, this element implemented the HTMLSpanElement interface instead of the standard HTMLElement interface.
html.elements.cite 📋Firefox11/9/2004 Chrome12/11/20081493
html.elements.code 📋Firefox11/9/2004 Chrome12/11/20081493
html.elements.col 📋Firefox11/9/2004 Chrome12/11/20081493
html.elements.col.align 📋Firefox11/9/2004 Chrome12/11/20081493
html.elements.col.span 📋Firefox11/9/2004 Chrome12/11/20081493
html.elements.col.valign 📋Firefox11/9/2004 Chrome12/11/20081493
html.elements.col.width 📋Firefox11/9/2004 Chrome12/11/20081493
html.elements.colgroup 📋Firefox11/9/2004 Chrome12/11/20081493
html.elements.colgroup.align 📋Firefox11/9/2004 Chrome12/11/20081493
html.elements.colgroup.span 📋Firefox11/9/2004 Chrome12/11/20081493
html.elements.colgroup.valign 📋Firefox11/9/2004 Chrome12/11/20081493
html.elements.colgroup.width 📋Firefox11/9/2004 Chrome12/11/20081493
html.elements.dd 📋Firefox11/9/2004 Chrome12/11/20081493
Firefox: Before Firefox 4, this element was implemented using the HTMLSpanElement interface instead of HTMLElement.
html.elements.del 📋Firefox11/9/2004 Chrome12/11/20081493
html.elements.del.cite Firefox11/9/2004 Chrome12/11/20081493
html.elements.del.datetime Firefox11/9/2004 Chrome12/11/20081493
html.elements.dir 📋Firefox11/9/2004 Chrome12/11/20081493
html.elements.dir.compact Firefox11/9/2004 Chrome12/11/20081493
html.elements.div 📋Firefox11/9/2004 Chrome12/11/20081493
html.elements.div.align Firefox11/9/2004 Chrome12/11/20081493
html.elements.dl 📋Firefox11/9/2004 Chrome12/11/20081493
html.elements.dt 📋Firefox11/9/2004 Chrome12/11/20081493
html.elements.em 📋Firefox11/9/2004 Chrome12/11/20081493
html.elements.embed 📋Firefox11/9/2004 Chrome12/11/20081493
html.elements.embed.align 📋Firefox11/9/2004 Chrome12/11/20081493
html.elements.embed.height 📋Firefox11/9/2004 Chrome12/11/20081493
html.elements.embed.name 📋Firefox11/9/2004 Chrome12/11/20081493
html.elements.embed.src 📋Firefox11/9/2004 Chrome12/11/20081493
html.elements.embed.type 📋Firefox11/9/2004 Chrome12/11/20081493
html.elements.embed.width 📋Firefox11/9/2004 Chrome12/11/20081493
html.elements.fieldset 📋Firefox11/9/2004 Chrome12/11/20081493
Chrome: Before version 86, this element did not support flexbox and grid layouts within this element. See bug 41027853.Chrome Android: Before version 86, this element did not support flexbox and grid layouts within this element. See bug 41027853.Edge: Before version 86, this element did not support flexbox and grid layouts within this element. See bug 4511145.Quest Browser: Before version 12.0, this element did not support flexbox and grid layouts within this element. See bug 41027853.Samsung Internet: Before version 14.0, this element did not support flexbox and grid layouts within this element. See bug 41027853.WebView Android: Before version 86, this element did not support flexbox and grid layouts within this element. See bug 41027853.
html.elements.fieldset.form 📋Firefox11/9/2004 Chrome12/11/20081493
html.elements.font 📋Firefox11/9/2004 Chrome12/11/20081493
html.elements.font.color Firefox11/9/2004 Chrome12/11/20081493
html.elements.font.face Firefox11/9/2004 Chrome12/11/20081493
html.elements.font.size Firefox11/9/2004 Chrome12/11/20081493
html.elements.form 📋Firefox11/9/2004 Chrome12/11/20081493
html.elements.form.accept-charset 📋Firefox11/9/2004 Chrome12/11/20081493
html.elements.form.action 📋Firefox11/9/2004 Chrome12/11/20081493
html.elements.form.enctype 📋Firefox11/9/2004 Chrome12/11/20081493
html.elements.form.method 📋Firefox11/9/2004 Chrome12/11/20081493
html.elements.form.name 📋Firefox11/9/2004 Chrome12/11/20081493
html.elements.form.target 📋Firefox11/9/2004 Chrome12/11/20081493
html.elements.frame 📋Firefox11/9/2004 Chrome12/11/20081493
html.elements.frame.frameborder Firefox11/9/2004 Chrome12/11/20081493
html.elements.frame.marginheight Firefox11/9/2004 Chrome12/11/20081493
html.elements.frame.marginwidth Firefox11/9/2004 Chrome12/11/20081493
html.elements.frame.name Firefox11/9/2004 Chrome12/11/20081493
html.elements.frame.noresize Firefox11/9/2004 Chrome12/11/20081493
html.elements.frame.scrolling Firefox11/9/2004 Chrome12/11/20081493
html.elements.frame.src Firefox11/9/2004 Chrome12/11/20081493
html.elements.frameset 📋Firefox11/9/2004 Chrome12/11/20081493
html.elements.frameset.cols Firefox11/9/2004 Chrome12/11/20081493
html.elements.frameset.rows Firefox11/9/2004 Chrome12/11/20081493
html.elements.h1 📋Firefox11/9/2004 Chrome12/11/20081493
html.elements.h2 📋Firefox11/9/2004 Chrome12/11/20081493
html.elements.h3 📋Firefox11/9/2004 Chrome12/11/20081493
html.elements.h4 📋Firefox11/9/2004 Chrome12/11/20081493
html.elements.h5 📋Firefox11/9/2004 Chrome12/11/20081493
html.elements.h6 📋Firefox11/9/2004 Chrome12/11/20081493
html.elements.head 📋Firefox11/9/2004 Chrome12/11/20081493
html.elements.hr 📋Firefox11/9/2004 Chrome12/11/20081493
html.elements.hr.align Firefox11/9/2004 Chrome12/11/20081493
html.elements.hr.noshade Firefox11/9/2004 Chrome12/11/20081493
html.elements.hr.size Firefox11/9/2004 Chrome12/11/20081493
html.elements.hr.width Firefox11/9/2004 Chrome12/11/20081493
html.elements.html 📋Firefox11/9/2004 Chrome12/11/20081493
html.elements.html.version 📋Firefox11/9/2004 Chrome12/11/20081493
html.elements.html.xmlns Firefox11/9/2004 Chrome12/11/20081493
html.elements.i 📋Firefox11/9/2004 Chrome12/11/20081493
html.elements.iframe 📋Firefox11/9/2004 Chrome12/11/20081493
Firefox: The resize CSS property doesn't have any effect on this element due to bug 680823.Firefox for Android: The resize CSS property doesn't have any effect on this element due to bug 680823.Safari: Safari has a bug that prevents iframes from loading if the iframe element was hidden when added to the page. iframeElement.src = iframeElement.src should cause it to load the iframe.Safari on iOS: Safari on iOS has a bug that prevents iframes from loading if the iframe element was hidden when added to the page. iframeElement.src = iframeElement.src should cause it to load the iframe.WebView on iOS: WebView on iOS has a bug that prevents iframes from loading if the iframe element was hidden when added to the page. iframeElement.src = iframeElement.src should cause it to load the iframe.
html.elements.iframe.align 📋Firefox11/9/2004 Chrome12/11/20081493
html.elements.iframe.frameborder 📋Firefox11/9/2004 Chrome12/11/20081493
html.elements.iframe.height 📋Firefox11/9/2004 Chrome12/11/20081493
html.elements.iframe.longdesc 📋Firefox11/9/2004 Chrome12/11/20081493
html.elements.iframe.marginheight 📋Firefox11/9/2004 Chrome12/11/20081493
html.elements.iframe.marginwidth 📋Firefox11/9/2004 Chrome12/11/20081493
html.elements.iframe.name 📋Firefox11/9/2004 Chrome12/11/20081493
html.elements.iframe.scrolling 📋Firefox11/9/2004 Chrome12/11/20081493
html.elements.iframe.src 📋Firefox11/9/2004 Chrome12/11/20081493
html.elements.iframe.width 📋Firefox11/9/2004 Chrome12/11/20081493
html.elements.img 📋Firefox11/9/2004 Chrome12/11/20081493
html.elements.img.align 📋Firefox11/9/2004 Chrome12/11/20081493
html.elements.img.alt 📋Firefox11/9/2004 Chrome12/11/20081493
html.elements.img.border 📋Firefox11/9/2004 Chrome12/11/20081493
html.elements.img.height 📋Firefox11/9/2004 Chrome12/11/20081493
html.elements.img.hspace 📋Firefox11/9/2004 Chrome12/11/20081493
html.elements.img.ismap 📋Firefox11/9/2004 Chrome12/11/20081493
html.elements.img.longdesc 📋Firefox11/9/2004 Chrome12/11/20081493
html.elements.img.name 📋Firefox11/9/2004 Chrome12/11/20081493
html.elements.img.src 📋Firefox11/9/2004 Chrome12/11/20081493
html.elements.img.usemap 📋Firefox11/9/2004 Chrome12/11/20081493
html.elements.img.vspace 📋Firefox11/9/2004 Chrome12/11/20081493
html.elements.img.width 📋Firefox11/9/2004 Chrome12/11/20081493
html.elements.input 📋Firefox11/9/2004 Chrome12/11/20081493
Firefox: Before Firefox 89, manipulating the content of <input> elements using Document.execCommand() commands requires workarounds (see bug 1220696).Firefox for Android: Before Firefox for Android 89, manipulating the content of <input> elements using Document.execCommand() commands requires workarounds (see bug 1220696).
html.elements.input.accept 📋Firefox11/9/2004 Chrome12/11/20081493
Safari on iOS: Does not support audio/* MIME type. See bug 242110.WebView on iOS: Does not support audio/* MIME type. See bug 242110.
html.elements.input.align 📋Firefox11/9/2004 Chrome12/11/20081493
html.elements.input.alt 📋Firefox11/9/2004 Chrome12/11/20081493
html.elements.input.checked 📋Firefox11/9/2004 Chrome12/11/20081493
html.elements.input.disabled 📋Firefox11/9/2004 Chrome12/11/20081493
html.elements.input.form 📋Firefox11/9/2004 Chrome12/11/20081493
html.elements.input.maxlength 📋Firefox11/9/2004 Chrome12/11/20081493
html.elements.input.name 📋Firefox11/9/2004 Chrome12/11/20081493
html.elements.input.readonly 📋Firefox11/9/2004 Chrome12/11/20081493
html.elements.input.size 📋Firefox11/9/2004 Chrome12/11/20081493
html.elements.input.src 📋Firefox11/9/2004 Chrome12/11/20081493
html.elements.input.type_button 📋Firefox11/9/2004 Chrome12/11/20081493
html.elements.input.type_checkbox 📋Firefox11/9/2004 Chrome12/11/20081493
html.elements.input.type_file 📋Firefox11/9/2004 Chrome12/11/20081493
Firefox: You can set as well as get the value of HTMLInputElement.files in all modern browsers; this was most recently added to Firefox, in version 57 (see bug 1384030).
html.elements.input.type_hidden 📋Firefox11/9/2004 Chrome12/11/20081493
html.elements.input.type_image 📋Firefox11/9/2004 Chrome12/11/20081493
html.elements.input.type_password 📋Firefox11/9/2004 Chrome12/11/20081493
html.elements.input.type_radio 📋Firefox11/9/2004 Chrome12/11/20081493
html.elements.input.type_reset 📋Firefox11/9/2004 Chrome12/11/20081493
Firefox: Unlike other browsers, Firefox by default persists the dynamic disabled state of a <button> across page loads. Use the autocomplete attribute to control this feature.Firefox for Android: Unlike other browsers, Firefox for Android by default persists the dynamic disabled state of a <button> across page loads. Use the autocomplete attribute to control this feature.
html.elements.input.type_submit 📋Firefox11/9/2004 Chrome12/11/20081493
Firefox: Unlike other browsers, Firefox by default persists the dynamic disabled state of a <button> across page loads. Use the autocomplete attribute to control this feature.Firefox for Android: Unlike other browsers, Firefox for Android by default persists the dynamic disabled state of a <button> across page loads. Use the autocomplete attribute to control this feature.
html.elements.input.type_text 📋Firefox11/9/2004 Chrome12/11/20081493
html.elements.input.type_url 📋Firefox11/9/2004 Chrome12/11/20081493
html.elements.input.usemap 📋Firefox11/9/2004 Chrome12/11/20081493
html.elements.ins 📋Firefox11/9/2004 Chrome12/11/20081493
html.elements.ins.cite Firefox11/9/2004 Chrome12/11/20081493
html.elements.ins.datetime Firefox11/9/2004 Chrome12/11/20081493
html.elements.kbd 📋Firefox11/9/2004 Chrome12/11/20081493
Firefox: Before Firefox 4, creating a <kbd> element incorrectly resulted in an HTMLSpanElement object, instead of the expected HTMLElement.
html.elements.label 📋Firefox11/9/2004 Chrome12/11/20081493
html.elements.label.for 📋Firefox11/9/2004 Chrome12/11/20081493
html.elements.legend 📋Firefox11/9/2004 Chrome12/11/20081493
html.elements.legend.align Firefox11/9/2004 Chrome12/11/20081493
html.elements.li 📋Firefox11/9/2004 Chrome12/11/20081493
html.elements.li.type 📋Firefox11/9/2004 Chrome12/11/20081493
html.elements.li.value 📋Firefox11/9/2004 Chrome12/11/20081493
html.elements.link 📋Firefox11/9/2004 Chrome12/11/20081493
html.elements.link.charset 📋Firefox11/9/2004 Chrome12/11/20081493
html.elements.link.disabled 📋Firefox11/9/2004 Chrome12/11/20081493
Chrome: In Chrome and other Blink-based browsers, adding the disabled attribute using JavaScript does not remove the stylesheet from document.styleSheets.Chrome Android: In Chrome Android and other Blink-based browsers, adding the disabled attribute using JavaScript does not remove the stylesheet from document.styleSheets.Edge: Since Edge 79, adding the disabled attribute using JavaScript does not remove the stylesheet from document.styleSheets.Quest Browser: In Quest Browser and other Blink-based browsers, adding the disabled attribute using JavaScript does not remove the stylesheet from document.styleSheets.Opera: In Chrome and other Blink-based browsers, adding the disabled attribute using JavaScript does not remove the stylesheet from document.styleSheets.Opera Android: In Chrome and other Blink-based browsers, adding the disabled attribute using JavaScript does not remove the stylesheet from document.styleSheets.Samsung Internet: In Samsung Internet and other Blink-based browsers, adding the disabled attribute using JavaScript does not remove the stylesheet from document.styleSheets.WebView Android: In WebView Android and other Blink-based browsers, adding the disabled attribute using JavaScript does not remove the stylesheet from document.styleSheets.
html.elements.link.href 📋Firefox11/9/2004 Chrome12/11/20081493
html.elements.link.hreflang 📋Firefox11/9/2004 Chrome12/11/20081493
html.elements.link.media 📋Firefox11/9/2004 Chrome12/11/20081493
html.elements.link.rel 📋Firefox11/9/2004 Chrome12/11/20081493
html.elements.link.rev 📋Firefox11/9/2004 Chrome12/11/20081493
html.elements.link.target 📋Firefox11/9/2004 Chrome12/11/20081493
html.elements.link.type 📋Firefox11/9/2004 Chrome12/11/20081493
html.elements.map 📋Firefox11/9/2004 Chrome12/11/20081493
Firefox: Before Firefox 5, in Quirks Mode, empty maps were no longer skipped over in favor of non-empty ones when matching.Firefox: Before Firefox 17, the default styling of the <map> HTML element was display: block;. This is now display: inline; and matches the behavior of the other browsers. It was already the case in Quirks Mode.
html.elements.map.name Firefox11/9/2004 Chrome12/11/20081493
html.elements.marquee.behavior Firefox11/9/2004 Chrome12/11/20081493
html.elements.marquee.bgcolor Firefox11/9/2004 Chrome12/11/20081493
html.elements.marquee.direction Firefox11/9/2004 Chrome12/11/20081493
html.elements.marquee.height Firefox11/9/2004 Chrome12/11/20081493
html.elements.marquee.hspace Firefox6/17/2008 Chrome12/11/2008177
html.elements.marquee.loop Firefox6/17/2008 Chrome12/11/2008177
html.elements.marquee.scrollamount Firefox11/9/2004 Chrome12/11/20081493
html.elements.marquee.scrolldelay Firefox11/9/2004 Chrome12/11/20081493
html.elements.marquee.truespeed Firefox6/17/2008 Chrome12/11/2008177
html.elements.marquee.vspace Firefox6/17/2008 Chrome12/11/2008177
html.elements.marquee.width Firefox11/9/2004 Chrome12/11/20081493
html.elements.menu 📋Firefox11/9/2004 Chrome12/11/20081493
html.elements.meta 📋Firefox11/9/2004 Chrome12/11/20081493
html.elements.meta.charset 📋Firefox11/9/2004 Chrome12/11/20081493
html.elements.meta.content 📋Firefox11/9/2004 Chrome12/11/20081493
html.elements.meta.http-equiv 📋Firefox11/9/2004 Chrome12/11/20081493
html.elements.meta.http-equiv.refresh 📋Firefox11/9/2004 Chrome12/11/20081493
html.elements.meta.name 📋Firefox11/9/2004 Chrome12/11/20081493
html.elements.meta.scheme 📋Firefox11/9/2004 Chrome12/11/20081493
html.elements.nobr 📋Firefox11/9/2004 Chrome12/11/20081493
html.elements.noembed 📋Firefox11/9/2004 Chrome12/11/20081493
html.elements.noframes 📋Firefox11/9/2004 Chrome12/11/20081493
html.elements.noscript 📋Firefox11/9/2004 Chrome12/11/20081493
html.elements.object 📋Firefox11/9/2004 Chrome12/11/20081493
html.elements.object.archive 📋Firefox11/9/2004 Chrome12/11/20081493
html.elements.object.border 📋Firefox11/9/2004 Chrome12/11/20081493
html.elements.object.classid 📋Firefox11/9/2004 Chrome12/11/20081493
html.elements.object.codetype 📋Firefox11/9/2004 Chrome12/11/20081493
html.elements.object.data 📋Firefox11/9/2004 Chrome12/11/20081493
html.elements.object.declare 📋Firefox11/9/2004 Chrome12/11/20081493
html.elements.object.form 📋Firefox11/9/2004 Chrome12/11/20081493
html.elements.object.height 📋Firefox11/9/2004 Chrome12/11/20081493
html.elements.object.name 📋Firefox11/9/2004 Chrome12/11/20081493
html.elements.object.standby 📋Firefox11/9/2004 Chrome12/11/20081493
html.elements.object.type 📋Firefox11/9/2004 Chrome12/11/20081493
html.elements.object.usemap 📋Firefox11/9/2004 Chrome12/11/20081493
html.elements.object.width 📋Firefox11/9/2004 Chrome12/11/20081493
html.elements.ol 📋Firefox11/9/2004 Chrome12/11/20081493
html.elements.ol.compact Firefox11/9/2004 Chrome12/11/20081493
html.elements.ol.start 📋Firefox11/9/2004 Chrome12/11/20081493
html.elements.ol.type 📋Firefox11/9/2004 Chrome12/11/20081493
html.elements.optgroup 📋Firefox11/9/2004 Chrome12/11/20081493
html.elements.optgroup.disabled 📋Firefox11/9/2004 Chrome12/11/20081493
Safari: Before Safari 7, the attribute can be set, but has no effect.Safari on iOS: The attribute can be set, but has no effect.WebView on iOS: The attribute can be set, but has no effect.
html.elements.optgroup.label 📋Firefox11/9/2004 Chrome12/11/20081493
html.elements.option 📋Firefox11/9/2004 Chrome12/11/20081493
html.elements.option.disabled 📋Firefox11/9/2004 Chrome12/11/20081493
html.elements.option.label 📋Firefox11/9/2004 Chrome12/11/20081493
Firefox: Before 77, Firefox didn't display the value of the label attribute as option text if element's content was empty. See bug 40545.Firefox: Historically, Firefox has allowed keyboard and mouse events to bubble up from the <option> element to the parent <select> element, although this behavior is inconsistent across many browsers. For better Web compatibility (and for technical reasons), they will not bubble up when Firefox is in multi-process mode and the <select> element is displayed as a drop-down list. The behavior is unchanged if the <select> is presented inline and it has either the multiple attribute defined or a size attribute set to more than 1. Rather than watching <option> elements for events, you should watch for change events on <select>. See bug 1090602 for details.Firefox: When Mozilla introduced dedicated content threads to Firefox (through the Electrolysis, or e10s, project), support for styling <option> elements was removed temporarily. Starting in Firefox 54, you can apply foreground and background colors to <option> elements again, using the color and background-color CSS properties. See bug 910022 for more information. Note that this is still disabled in Linux due to lack of contrast (see bug 1338283 for progress on this).Firefox for Android: Before 77, Firefox didn't display the value of the label attribute as option text if element's content was empty. See bug 40545.
html.elements.option.selected 📋Firefox11/9/2004 Chrome12/11/20081493
html.elements.option.value 📋Firefox11/9/2004 Chrome12/11/20081493
html.elements.p 📋Firefox11/9/2004 Chrome12/11/20081493
html.elements.param 📋Firefox11/9/2004 Chrome12/11/20081493
html.elements.param.name Firefox11/9/2004 Chrome12/11/20081493
html.elements.param.type Firefox11/9/2004 Chrome12/11/20081493
html.elements.param.value Firefox11/9/2004 Chrome12/11/20081493
html.elements.param.valuetype Firefox11/9/2004 Chrome12/11/20081493
html.elements.pre 📋Firefox11/9/2004 Chrome12/11/20081493
html.elements.pre.width Firefox11/9/2004 Chrome12/11/20081493
Chrome: Specifying the width attribute has no layout effect.Chrome Android: Specifying the width attribute has no layout effect.Edge: Specifying the width attribute has no layout effect.Firefox: Since Firefox 29, specifying the width attribute has no layout effect.Firefox for Android: Since Firefox for Android 29, specifying the width attribute has no layout effect.Internet Explorer: Specifying the width attribute has no layout effect.Quest Browser: Specifying the width attribute has no layout effect.Opera: Specifying the width attribute has no layout effect.Opera Android: Specifying the width attribute has no layout effect.Safari: Specifying the width attribute has no layout effect.Safari on iOS: Specifying the width attribute has no layout effect.Samsung Internet: Specifying the width attribute has no layout effect.WebView Android: Specifying the width attribute has no layout effect.WebView on iOS: Specifying the width attribute has no layout effect.
html.elements.q 📋Firefox11/9/2004 Chrome12/11/20081493
html.elements.q.cite 📋Firefox11/9/2004 Chrome12/11/20081493
html.elements.s 📋Firefox11/9/2004 Chrome12/11/20081493
Firefox: Before Firefox 4, this element implemented the HTMLSpanElement interface instead of the standard HTMLElement interface.
html.elements.samp 📋Firefox11/9/2004 Chrome12/11/20081493
html.elements.script 📋Firefox11/9/2004 Chrome12/11/20081493
Firefox: Starting in Firefox 4, inserting <script> elements that have been created by calling document.createElement("script") no longer enforces execution in insertion order. This change lets Firefox properly abide by the specification. To make script-inserted external scripts execute in their insertion order, set .async=false on them.
html.elements.script.src 📋Firefox11/9/2004 Chrome12/11/20081493
html.elements.script.type 📋Firefox11/9/2004 Chrome12/11/20081493
html.elements.select 📋Firefox11/9/2004 Chrome12/11/20081493
Chrome: border-radius on <select> elements is ignored unless -webkit-appearance is overridden to an appropriate value.Chrome Android: border-radius on <select> elements is ignored unless -webkit-appearance is overridden to an appropriate value.Firefox: Historically, Firefox has allowed keyboard and mouse events to bubble up from the <option> element to the parent <select> element, although this behavior is inconsistent across many browsers. For better Web compatibility (and for technical reasons), when Firefox is in multi-process mode the <select> element is displayed as a drop-down list. The behavior is unchanged if the <select> is presented inline and it has either the multiple attribute defined or a size attribute set to more than 1. Rather than watching <option> elements for events, you should watch for change events on <select>. See bug 1090602 for details.Firefox for Android: Firefox for Android, by default, sets a background-image gradient on all <select multiple> elements. This can be disabled using background-image: none.Quest Browser: border-radius on <select> elements is ignored unless -webkit-appearance is overridden to an appropriate value.Safari: border-radius on <select> elements is ignored unless -webkit-appearance is overridden to an appropriate value.Safari on iOS: border-radius on <select> elements is ignored unless -webkit-appearance is overridden to an appropriate value.Samsung Internet: border-radius on <select> elements is ignored unless -webkit-appearance is overridden to an appropriate value.WebView Android: border-radius on <select> elements is ignored unless -webkit-appearance is overridden to an appropriate value.WebView on iOS: border-radius on <select> elements is ignored unless -webkit-appearance is overridden to an appropriate value.
html.elements.select.disabled 📋Firefox11/9/2004 Chrome12/11/20081493
html.elements.select.form 📋Firefox11/9/2004 Chrome12/11/20081493
html.elements.select.multiple 📋Firefox11/9/2004 Chrome12/11/20081493
html.elements.select.name 📋Firefox11/9/2004 Chrome12/11/20081493
html.elements.select.size 📋Firefox11/9/2004 Chrome12/11/20081493
html.elements.small 📋Firefox11/9/2004 Chrome12/11/20081493
html.elements.span 📋Firefox11/9/2004 Chrome12/11/20081493
html.elements.strike 📋Firefox11/9/2004 Chrome12/11/20081493
Firefox: Before Firefox 4, this element implemented the HTMLSpanElement interface instead of the standard HTMLElement interface.Firefox for Android: Before Firefox for Android 4, this element implemented the HTMLSpanElement interface instead of the standard HTMLElement interface.
html.elements.strong 📋Firefox11/9/2004 Chrome12/11/20081493
Firefox: Before Firefox 4, creating a <strong> element incorrectly resulted in an HTMLSpanElement object, instead of the expected HTMLElement.
html.elements.style 📋Firefox11/9/2004 Chrome12/11/20081493
html.elements.style.media 📋Firefox11/9/2004 Chrome12/11/20081493
html.elements.style.type 📋Firefox11/9/2004 Chrome12/11/20081493
Firefox: Before 75, Firefox accepted any CSS media (MIME) type, with optional parameters. Starting in 75, this has been restricted to the string 'text/css', per the spec.
html.elements.sub 📋Firefox11/9/2004 Chrome12/11/20081493
html.elements.sup 📋Firefox11/9/2004 Chrome12/11/20081493
html.elements.table 📋Firefox11/9/2004 Chrome12/11/20081493
html.elements.table.align Firefox11/9/2004 Chrome12/11/20081493
html.elements.table.bgcolor Firefox11/9/2004 Chrome12/11/20081493
html.elements.table.border Firefox11/9/2004 Chrome12/11/20081493
html.elements.table.cellpadding Firefox11/9/2004 Chrome12/11/20081493
html.elements.table.cellspacing Firefox11/9/2004 Chrome12/11/20081493
html.elements.table.frame Firefox11/9/2004 Chrome12/11/20081493
html.elements.table.rules Firefox11/9/2004 Chrome12/11/20081493
html.elements.table.summary Firefox11/9/2004 Chrome12/11/20081493
html.elements.table.width Firefox11/9/2004 Chrome12/11/20081493
html.elements.tbody 📋Firefox11/9/2004 Chrome12/11/20081493
html.elements.tbody.align Firefox11/9/2004 Chrome12/11/20081493
html.elements.tbody.bgcolor Firefox11/9/2004 Chrome12/11/20081493
html.elements.tbody.valign Firefox11/9/2004 Chrome12/11/20081493
html.elements.td 📋Firefox11/9/2004 Chrome12/11/20081493
html.elements.td.abbr Firefox11/9/2004 Chrome12/11/20081493
html.elements.td.align Firefox11/9/2004 Chrome12/11/20081493
html.elements.td.axis Firefox11/9/2004 Chrome12/11/20081493
html.elements.td.bgcolor Firefox11/9/2004 Chrome12/11/20081493
html.elements.td.colspan Firefox11/9/2004 Chrome12/11/20081493
html.elements.td.headers Firefox11/9/2004 Chrome12/11/20081493
html.elements.td.rowspan Firefox11/9/2004 Chrome12/11/20081493
html.elements.td.scope Firefox11/9/2004 Chrome12/11/20081493
html.elements.td.valign Firefox11/9/2004 Chrome12/11/20081493
html.elements.td.width Firefox11/9/2004 Chrome12/11/20081493
html.elements.textarea 📋Firefox11/9/2004 Chrome12/11/20081493
Firefox: Before Firefox 6, when a <textarea> was focused, the insertion point was placed at the end of the text by default. Other major browsers place the insertion point at the beginning of the text.Firefox: A default background-image gradient is applied to all <textarea> elements, which can be disabled using background-image: none.Firefox: Before Firefox 89, manipulating the content of <textarea> elements using Document.execCommand() commands requires workarounds (see bug 1220696).Firefox for Android: Before Firefox for Android 6, when a <textarea> was focused, the insertion point was placed at the end of the text by default. Other major browsers place the insertion point at the beginning of the text.Firefox for Android: A default background-image gradient is applied to all <textarea> elements, which can be disabled using background-image: none.Firefox for Android: Before Firefox for Android 89, manipulating the content of <textarea> elements using Document.execCommand() commands requires workarounds (see bug 1220696).Safari on iOS: Unlike other major browsers, a default style of opacity: 0.4 is applied to disabled <textarea> elements.WebView on iOS: Unlike other major browsers, a default style of opacity: 0.4 is applied to disabled <textarea> elements.
html.elements.textarea.cols 📋Firefox11/9/2004 Chrome12/11/20081493
html.elements.textarea.disabled 📋Firefox11/9/2004 Chrome12/11/20081493
html.elements.textarea.form 📋Firefox11/9/2004 Chrome12/11/20081493
html.elements.textarea.name 📋Firefox11/9/2004 Chrome12/11/20081493
html.elements.textarea.readonly 📋Firefox11/9/2004 Chrome12/11/20081493
html.elements.textarea.rows 📋Firefox11/9/2004 Chrome12/11/20081493
html.elements.tfoot 📋Firefox11/9/2004 Chrome12/11/20081493
html.elements.tfoot.align Firefox11/9/2004 Chrome12/11/20081493
html.elements.tfoot.bgcolor Firefox11/9/2004 Chrome12/11/20081493
html.elements.tfoot.valign Firefox11/9/2004 Chrome12/11/20081493
html.elements.th 📋Firefox11/9/2004 Chrome12/11/20081493
html.elements.th.abbr Firefox11/9/2004 Chrome12/11/20081493
html.elements.th.align Firefox11/9/2004 Chrome12/11/20081493
html.elements.th.axis Firefox11/9/2004 Chrome12/11/20081493
html.elements.th.bgcolor Firefox11/9/2004 Chrome12/11/20081493
html.elements.th.colspan Firefox11/9/2004 Chrome12/11/20081493
html.elements.th.headers Firefox11/9/2004 Chrome12/11/20081493
html.elements.th.rowspan Firefox11/9/2004 Chrome12/11/20081493
html.elements.th.scope Firefox11/9/2004 Chrome12/11/20081493
html.elements.th.valign Firefox11/9/2004 Chrome12/11/20081493
html.elements.th.width Firefox11/9/2004 Chrome12/11/20081493
html.elements.thead 📋Firefox11/9/2004 Chrome12/11/20081493
Safari: Backgrounds applied to <thead> elements will be applied to each table cell, rather than the entire header. To mimic the behavior of other browsers, set the background-attachment CSS property to fixed.Safari on iOS: Backgrounds applied to <thead> elements will be applied to each table cell, rather than the entire header. To mimic the behavior of other browsers, set the background-attachment CSS property to fixed.WebView on iOS: Backgrounds applied to <thead> elements will be applied to each table cell, rather than the entire header. To mimic the behavior of other browsers, set the background-attachment CSS property to fixed.
html.elements.thead.align Firefox11/9/2004 Chrome12/11/20081493
html.elements.thead.bgcolor Firefox11/9/2004 Chrome12/11/20081493
html.elements.thead.valign Firefox11/9/2004 Chrome12/11/20081493
html.elements.title 📋Firefox11/9/2004 Chrome12/11/20081493
html.elements.tr 📋Firefox11/9/2004 Chrome12/11/20081493
html.elements.tr.align Firefox11/9/2004 Chrome12/11/20081493
html.elements.tr.bgcolor Firefox11/9/2004 Chrome12/11/20081493
html.elements.tr.valign Firefox11/9/2004 Chrome12/11/20081493
html.elements.tt 📋Firefox11/9/2004 Chrome12/11/20081493
Firefox: Before Firefox 4, this element implemented the HTMLSpanElement interface instead of the standard HTMLElement interface.Firefox for Android: Before Firefox for Android 4, this element implemented the HTMLSpanElement interface instead of the standard HTMLElement interface.
html.elements.u 📋Firefox11/9/2004 Chrome12/11/20081493
Firefox: Before Firefox 4, this element implemented the HTMLSpanElement interface instead of the standard HTMLElement interface.
html.elements.ul 📋Firefox11/9/2004 Chrome12/11/20081493
html.elements.ul.compact 📋Firefox11/9/2004 Chrome12/11/20081493
html.elements.ul.type 📋Firefox11/9/2004 Chrome12/11/20081493
html.elements.var 📋Firefox11/9/2004 Chrome12/11/20081493
html.elements.wbr 📋Firefox11/9/2004 Chrome12/11/20081493
html.elements.xmp 📋Firefox11/9/2004 Chrome12/11/20081493
Firefox: Before Firefox 4, this element implemented the HTMLSpanElement interface instead of the standard HTMLElement interface.Firefox for Android: Before Firefox for Android 4, this element implemented the HTMLSpanElement interface instead of the standard HTMLElement interface.
html.global_attributes.accesskey 📋Firefox11/9/2004 Chrome12/11/20081493
html.global_attributes.class 📋Firefox11/9/2004 Chrome12/11/20081493
html.global_attributes.contenteditable 📋Firefox6/17/2008 Chrome12/11/2008177
html.global_attributes.dir 📋Firefox11/9/2004 Chrome12/11/20081493
html.global_attributes.lang 📋Firefox11/9/2004 Chrome12/11/20081493
html.global_attributes.style 📋Firefox11/9/2004 Chrome12/11/20081493
html.global_attributes.tabindex 📋Firefox11/29/2005 Chrome12/11/20081108
html.global_attributes.title 📋Firefox11/9/2004 Chrome12/11/20081493