Ticket #688 - Fix for Store#find returning on first prop match

This fixes an issue where Store#find would return any item that had just 1 property match. It now goes through every property and unless it finds a property that does NOT match the query, it assumes it's a match.

ZOMG this commit is from Github HQ!!

Ignores the "possible strict validations".

Controller.prototype.removeItem did not check if the item was available
via the DOM before calling removeChild.  If you were only viewing
"active" and clicked the "Clear completed" button it would result in an
error.  Wrapped the remvoeChild call in an if statement to validate
existence of the elememnt.

Add AngularFire and change mailing list link to new Firebase + Angular Google Group

link to the spec where it’s mentioned in the legend

I reworded that legend entry so that "spec" is its own word, because it looked a little weird to have part of a word boldened (links are boldened).

Yay

Bower all the things

Use bower for the site

- updated Twitter Bootstrap to 2.3.2 (required small popover change)
- updated jQuery to 1.10
- used bower for dep management

`git grep assets/jq` didn't yield any results except for the front page

As single commit to allow for emergency reverts. :)

clarify legend on home page by restyling

style "Maroon" in the legend like the labs items it refers to

make the legend stand apart from the list more

and refactor the .labs-example styles

The `<b>` element is perfectly legitimate here: http://www.whatwg.org/specs/web-apps/current-work/multipage/text-level-semantics.html#the-b-element . I am making the '*'s stand out more without conveying extra importance or alternate voice or mood.

style legend with a grey border

to show that it's a different type of content from the lists above

also changed from a `div` with `p`s to a `ul`, as that matches semantics more closely

move legend under the first app list

and remove grey border around legend, since the legend is prominent enough now without it

done at request of https://github.com/tastejs/todomvc/pull/675#issuecomment-23901896

Should fix #677

remove 'order' attribute from comment

fix Meteor description by adding missing space

don't mention 'order' as a default attribute since the attribute no longer exists

Update todoEscape.js

I think you meant escape :)

TodoMVC Mozart example

Unit tests for Flight example

Upgraded to flight 1.0.4 which removed `Component#bind` in favor of the native
or polyfilled `Function#bind` and used the new require.js bower format.

Waiting for @phuu to upgrade to Flight 1.1. :)