You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It seems very new. However, From Safari's blog post:
We are excited to be the first browser to ship this new <search> element, now supported in Safari 17.0.
...
Browsers without support for the search element will recognize there is an element present, and they will recognize any attributes it has — including roles, IDs, and classes. It will simply behave like a generic element, as if it were a <div>. Because of this, we recommend you include an ARIA search role on the <search> element for now. By using <search role="search">, you will ensure every user has the intended experience. And in the future, when all browsers have support, you can drop the ARIA search role.
In the meantime, you can start using <search> today with confidence, long before a significant percent [sic] of your audience use browsers with support.
So it seems that even though only one browser supports the element, we can start using it, and nothing will break.
There's also a new
<search>
element:https://webkit.org/blog/14445/webkit-features-in-safari-17-0/
Perhaps we can replace this
<div>
?The article mentions the ARIA
role="search"
should be kept until there's wider browser support.Originally posted by @hugovk in #11697 (comment)
The text was updated successfully, but these errors were encountered: