-
-
Notifications
You must be signed in to change notification settings - Fork 8.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Missing support for <search>
element
#9247
Comments
Hey, got the same error on an Vue + Astro project. I tried to solve the warning with |
There is an idea when this will be merged? |
Using the <search> element caused a console warning, since Vue doesn't yet support it. See vuejs/core#9247
@lenaschimmel You can tell Vue to treat the I adjusted my Vite configuration like this: export default defineConfig({
plugins: [
vue({
template: {
compilerOptions: {
isCustomElement: (tag) => ["search"].includes(tag),
},
},
}),
],
}); I used an array to define the tags to have the option to add more if necessary. There are alternative ways if you don’t use Vite: https://vuejs.org/guide/extras/web-components.html#skipping-component-resolution |
Vue version
3.3.4
Link to minimal reproduction
https://play.vuejs.org/#eNqNUclOwzAQ/ZXI5yY+lFNVUAH1AAdAwNGXEA+tizeNx21R1X/HcUoIZVFv9rxnv2V27NL7ah2BTdiUwHhdE1wIWxTTADU2y3xON2V9pILePZwL1kGCFbyj8p475f0nbMSU8Q6pNLWvVsHZpLFr+eIABMEmRZ60s2SivQu2JPJhwnkjbXomQas1VhaIW2/4LNE4RkvKQCmdmY2rcXXGpQo0HFcQTPmCbhMA0yeCjQYyyS6uAUsEKwEBT5U9ejaUPoJ+yLfqe2H3qRQKjbOvanFUSeOMVxrw3pNy9ns1tdZuc5tnhBH6LM0Smrdf5quw7TI9IGRng/xU4wKog+dPd7BN5x40TkZ9WMMf4CMEp2PrsaNdRSuT7QEvu73JG1Z28RzmWwIbPkO1RnMbmZ/3cf1P9C+7qe2+xf0H3EDoMg==
Steps to reproduce
Include a
<search>
element in a templateWhat is expected?
The element is picked up as a native element
What is actually happening?
System Info
No response
Any additional comments?
<search>
is a new HTML element that provides asearch
landmark, rather than requiringrole="search"
(https://developer.mozilla.org/en-US/docs/Web/HTML/Element/search). The element is supported in iOS/iPadOS 17, Safari 17 and Firefox 118.The text was updated successfully, but these errors were encountered: