-
Notifications
You must be signed in to change notification settings - Fork 27.2k
Boolean properties as HTML binary attributes #14761
Copy link
Copy link
Closed
Labels
area: coreIssues related to the framework runtimeIssues related to the framework runtimecore: binding & interpolationIssue related to property/attribute binding or text interpolationIssue related to property/attribute binding or text interpolationcore: inputs / outputsfeatureLabel used to distinguish feature request from other issuesLabel used to distinguish feature request from other issuesfeature: under considerationFeature request for which voting has completed and the request is now under considerationFeature request for which voting has completed and the request is now under consideration
Milestone
Metadata
Metadata
Assignees
Labels
area: coreIssues related to the framework runtimeIssues related to the framework runtimecore: binding & interpolationIssue related to property/attribute binding or text interpolationIssue related to property/attribute binding or text interpolationcore: inputs / outputsfeatureLabel used to distinguish feature request from other issuesLabel used to distinguish feature request from other issuesfeature: under considerationFeature request for which voting has completed and the request is now under considerationFeature request for which voting has completed and the request is now under consideration
I'm submitting a ... (check one with "x")
Current behavior
Currently when you have a boolean property and bind it to
true|falseyou have to use property binding, i.eExpected behavior
The following code snippet should set the
roundedproperty totrue:while the snippet bellow should bind it to
false:What is the motivation / use case for changing the behavior?
This mimics the behavior of HTML binary attributes as well as how React threads such properties.
Of course property binding to should still works.