This test was causing us issues on CI for several reasons. The first
being that we were touching the DOM outside of webdrivers promise loop
(via Q). The second cause of issues was that we were holding onto DOM
nodes for a long time after we first queried the DOM, allowing the
pointers to potentially go stale.

fix stale element errors

Drop the YUI app

By converting the find and click to a 1 op this avoides the issue of a
stale element.

From the official site:
	"The YUI library is no longer actively maintained. "

We shouldn't suggest anybody to use a framework which isn't active
anymore.

Ref http://yahooeng.tumblr.com/post/96098168666/important-announcement-regarding-yui

✋ bye sauce hello travis

🐛 Fix test routing selector bug

It was seeding too many items, thus making the tests freak out.

IE11 fix for Dojo example, fixes #1349.

Ref #1234

🎅 Update angular to latest

Due to the changes in
https://github.com/angular/angular.js/commit/71fc3f4fa0cd12eff335d57efed7c033554749f4
https://github.com/angular/angular.js/commit/d19504a179355d7801d59a8db0285a1322e04601

xref https://github.com/angular/angular.js/issues/11959

test id => class work

angular2: App Example

Update the FOAM example to the new UI, and also to latest FOAM

Updates to the `react-backbone` example

We don't use these anymore

For consistency