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

[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

When listening to a native event such as (window:mousemove) the component is marked for check.

Expected behavior

When using OnPush detectors, then the framework will check an OnPush component when any of its input properties changes, when it fires an event, or when an observable fires an event

Note: It says that the angular will only check it if an input changes, it fires an output, or an observable fires an output. I can see how this could be considered an observable but I wouldn't think of a native event as observable.

Minimal reproduction of the problem with instructions

https://plnkr.co/edit/CEDANBqgbbKkBHSkHnDk?p=preview

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

If a component wants to listen to a native event it has to manually listen to that event using browser apis if it wants to avoid the change detector. This isn't great.

Please tell us about your environment:

Angular version: 2.0.X

2.0.2, 2.1.2

Browser: [all | Chrome XX | Firefox XX | IE XX | Safari XX | Mobile Chrome XX | Android X.X Web Browser | iOS XX Safari | iOS XX UIWebView | iOS XX WKWebView ]

Language: [all | TypeScript X.X | ES6/7 | ES5]

Node (for AoT issues): node --version =

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

[x] bug report
[ ] 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

Reposted from router v3 repo via @choeller

When having 2 router-outlets in a child-component the aux-functionality works well, but as soon as you want to leave the child-route the following exception is thrown and the router stops working:

EXCEPTION: Error: Uncaught (in promise): Error: Outlet is not activated

the following plnkr demonstrates the behaviour:

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

the aux-outlet is defined in crisis-center.component.ts

My use-case is to have an encapsulated part of my application that deals with "Tasks". When selecting a task I want to open a sidebar and display some important information about the task (JIRA-like). I already got this working in my application, but when once entering the "tasks" part I can never leave it again.

Expected/desired behavior

Reproduction of the problem

If the current behavior is a bug or you can illustrate your feature request better with an example, please provide the steps to reproduce and if possible a minimal demo of the problem via https://plnkr.co or similar (you can use this template as a starting point: http://plnkr.co/edit/tpl:AvJOMERrnz94ekVua0u5).

What is the expected behavior?

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

Please tell us about your environment:

Angular version: 2.0.0-rc.X

Browser: [all | Chrome XX | Firefox XX | IE XX | Safari XX | Mobile Chrome XX | Android X.X Web Browser | iOS XX Safari | iOS XX UIWebView | iOS XX WKWebView ]

Language: [all | TypeScript X.X | ES6/7 | ES5 | Dart]