Find a better way for Protractor to sync with Angular

[hankduan]

In order to inject mock modules into Angular before it bootstraps, Protractor currently does this:

Protractor changes window.name before navigating to an Angular site. Angular sees this name, halts bootstrap. After Angular injects the mock modules, Angular resumes bootstrap. This would be fine, except window.name isn't persistent across location.assign().

The way protractor is syncing with Angular implies the following:

1. protractor cannot implement back or forward
2. if another site redirects to Angular, mock modules will not be injected unless the test reloads Angular (i.e. if non-Angular log in page redirects to Angular app)

Need to think of a new communication protocol between Angular/protractor

[Droogans]

I personally would love to see graceful degradation of Protractor's functionalities if you were to navigate to a non-angular app. Right now, some links are like landmines in that they crash the entire test if you click them.

[ishmaelthedestroyer]

+1

[hankduan]

see #1155

[juliemr]

Removing needs investigation, since this is in icebox.

[juliemr]

Examples of issues that this causes:

#2461
#2076

[juliemr]

Closing in favor of #3374