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/attribute-coercion.md
+6-6Lines changed: 6 additions & 6 deletions
Original file line number
Diff line number
Diff line change
@@ -14,7 +14,7 @@ This is a low-level internal API change and does not affect most developers.
14
14
Here is a high level summary of the changes:
15
15
16
16
- Drop the internal concept of enumerated attributes and treat those attributes the same as normal non-boolean attributes
17
-
-**BREAKING**: No longer removes attribute if value is boolean `false`. Instead, it's set as attr="false" instead. To remove the attribute, use `null` or `undefined`.
17
+
-**BREAKING**: No longer removes attribute if the value is boolean `false`. Instead, it's set as attr="false". To remove the attribute, use `null` or `undefined`.
18
18
19
19
For more information, read on!
20
20
@@ -34,10 +34,10 @@ The following table describes how Vue coerce "enumerated attributes" differently
0 commit comments