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
Copy file name to clipboardExpand all lines: src/guide/migration/custom-elements-interop.md
+7-7Lines changed: 7 additions & 7 deletions
Original file line number
Diff line number
Diff line change
@@ -8,7 +8,7 @@ badges:
8
8
## Overview
9
9
10
10
-**BREAKING:** The checks to determine whether tags should be treated as custom elements are now performed during template compilation, and should be configured via compiler options instead of runtime config.
11
-
-**BREAKING:** Special `is`prop usage is restricted to the reserved `<component>` tag only.
11
+
-**BREAKING:** Special `is`attribute usage is restricted to the reserved `<component>` tag only.
12
12
-**NEW:** To support 2.x use cases where `is` was used on native elements to work around native HTML parsing restrictions, prefix the value with `vue:` to resolve it as a Vue component.
13
13
14
14
## Autonomous Custom Elements
@@ -69,21 +69,21 @@ The Custom Elements specification provides a way to use custom elements as [Cust
69
69
<buttonis="plastic-button">Click Me!</button>
70
70
```
71
71
72
-
Vue's usage of the `is` special prop was simulating what the native attribute does before it was made universally available in browsers. However, in 2.x it was interpreted as rendering a Vue component with the name `plastic-button`. This blocks the native usage of Customized Built-in Element mentioned above.
72
+
Vue's usage of the `is` special attribute was simulating what the native attribute does before it was made universally available in browsers. However, in 2.x it was interpreted as rendering a Vue component with the name `plastic-button`. This blocks the native usage of Customized Built-in Element mentioned above.
73
73
74
-
In 3.0, we are limiting Vue's special treatment of the `is`prop to the `<component>` tag only.
74
+
In 3.0, we are limiting Vue's special treatment of the `is`attribute to the `<component>` tag only.
75
75
76
76
- When used on the reserved `<component>` tag, it will behave exactly the same as in 2.x;
77
-
- When used on normal components, it will behave like a normal prop:
77
+
- When used on normal components, it will behave like a normal attribute:
78
78
79
79
```html
80
80
<foois="bar" />
81
81
```
82
82
83
83
- 2.x behavior: renders the `bar` component.
84
-
- 3.x behavior: renders the `foo` component and passing the `is`prop.
84
+
- 3.x behavior: renders the `foo` component and passing the `is`attribute.
85
85
86
-
- When used on plain elements, it will be passed to the `createElement` call as the `is`prop, and also rendered as a native attribute. This supports the usage of customized built-in elements.
86
+
- When used on plain elements, it will be passed to the `createElement` call as the `is`attribute, and also rendered as a native attribute. This supports the usage of customized built-in elements.
87
87
88
88
```html
89
89
<buttonis="plastic-button">Click Me!</button>
@@ -105,7 +105,7 @@ In 3.0, we are limiting Vue's special treatment of the `is` prop to the `<compon
105
105
106
106
### 2.x Syntax
107
107
108
-
In Vue 2 we recommended working around with these restrictions by using the `is` prop on a native tag:
108
+
In Vue 2 we recommended working around with these restrictions by using the `is` attribute on a native tag:
0 commit comments