From 6d604bd0c04d381a9792523607b46ad88da1c13f Mon Sep 17 00:00:00 2001 From: Peter Burns Date: Tue, 15 Feb 2022 23:46:21 -0800 Subject: [PATCH] Update custom-elements-everywhere score See https://github.com/vuejs/core/issues/5401 --- src/guide/extras/web-components.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/guide/extras/web-components.md b/src/guide/extras/web-components.md index 047b845316..43fddbc748 100644 --- a/src/guide/extras/web-components.md +++ b/src/guide/extras/web-components.md @@ -6,7 +6,7 @@ We consider Vue and Web Components to be primarily complementary technologies. V ## Using Custom Elements in Vue -Vue [scores a perfect 100% in the Custom Elements Everywhere tests](https://custom-elements-everywhere.com/libraries/vue/results/results.html). Consuming custom elements inside a Vue application largely works the same as using native HTML elements, with a few things to keep in mind: +Vue [scores a 91% in the Custom Elements Everywhere tests](https://custom-elements-everywhere.com/#vue), with the only limitation being that [declarative event handlers do not support events named with upper case letters](https://github.com/vuejs/core/issues/5401). Consuming custom elements inside a Vue application largely works the same as using native HTML elements, with a few things to keep in mind: ### Skipping Component Resolution