parent
a89e57f1b1
commit
933433ceea
|
@ -330,10 +330,6 @@ table
|
|||
+makeExample('template-syntax/ts/app/app.component.html', 'style-binding-syntax-1')(format=".")
|
||||
</div>
|
||||
|
||||
.l-sub-section
|
||||
:marked
|
||||
According to this rule, we should write `[inner-h-t-m-l]` to access the element’s `innerHTML` property.
|
||||
Fortunately, the Angular template parser recognizes `inner-html` as an acceptable alias for `innerHTML`.
|
||||
:marked
|
||||
Let’s descend from the architectural clouds and look at each of these binding types in concrete detail.
|
||||
|
||||
|
@ -659,7 +655,7 @@ code-example(format="", language="html").
|
|||
|
||||
We can write our own two-way binding directive that follows this pattern if we're ever in the mood to do so.
|
||||
:marked
|
||||
Is `[{ngModel}]` all we need? Is there ever a reason to fall back to its expanded form?
|
||||
Is `[(ngModel)]` all we need? Is there ever a reason to fall back to its expanded form?
|
||||
|
||||
Well `NgModel` can only set the target property.
|
||||
What if we need to do something more or something different when the user changes the value?
|
||||
|
|
Loading…
Reference in New Issue