Issue 1:
I'm submitting a ... (check one with "x")

[ ] bug report => search github for a similar issue or PR before submitting
[x ] feature request
[ ] support request => Please do not submit support request here, instead see https://github.com/angular/angular/blob/master/CONTRIBUTING.md#question

Current behavior

I love the transition to one-way data flow in Angular 2+. But there seems to be a gap when it comes to implementing strict one-way data flow with input controls. If I understand correctly, if you want to do one-way data flow with an input, you can just use [ngModel] to pass in the source model value and then handle the change event to update the source model. The only problem with this is that if something goes wrong and that change event doesn't get handled correctly, the view and the model can get out of sync.

ReactJS has the concept of a 'controlled input' where there is a guarantee made that the view will always show the current model value. Meaning, if you don't manually update the model in response to a change event or something goes wrong, the view value will not change. It's a nice guarantee.

Without this guarantee, I'm a little more hesitant to do one-way data flow with inputs and without the one-way data flow it's hard to do stuff like immutability and you miss out on the simplification that can come from one-way data flow.

With things like radio/checkbox inputs, this isn't as big of a deal because it's not too difficult to role your own custom radio/checkbox that only reflects the model value and emits change events. The difficult one is the text input because it would be pretty intense to 'role your own' text input. :)

Expected behavior

It would be nice if there was a directive or official 'best practices' in the documentation for this scenario. I understand that it's not a trivial task to 'guarantee the model and view are always in sync.' (you might have to deal with stuff like cursor jump, etc.) And there might not be a one-size fits all solution but it would nice if there were at least some best practices in the documentation. I've considered a setup where you have a component wrapper directive around an input and when a change event is fired it would in turn fire it's own change event and then manually kick off a change detection (so would run outside the zone). Then after that finishes it would check the model value and if it's not the same as the view value, it would revert/update the view value to match the model.

Minimal reproduction of the problem with instructions

http://plnkr.co/edit/R91YQ2ddsd0SxOcKzUce?p=preview

What is the motivation / use case for changing the behavior?

To allow for immutable state (e.g. Redux) and full one-way data flow when dealing with inputs.

Please tell us about your environment:

all

Angular version: 2.0.X

all

Browser:

all

Language:

all

Thanks for all the great work!

Andy

Issue 2:
Hi,

I've been following the Tour of Heroes tutorial. I've noticed that the back link to return from the hero detail component to the dashboard or the list of heroes does not work properly on safari.

Environment:

Safari 9.1 on Mac OS X 10.11.4

Go to https://angular.io/resources/live-examples/toh-5/ts/plnkr.html

click on one hero on the dashboard => details appears

click on the back button at the button => the dashboard is empty !!!

I tested it on Firefox 45.0.1 and it works ok: in step 3 the dashboard is correctly populated.

thanks.

Brieuc