angular.js, branch v0.10.1

chore(release): cutting the angular 0.10.1 inexorable-juggernaut release

2011-09-09T08:01:46+00:00

docs(changelog): release notes for angular 0.10.1 inexorable-juggernaut

2011-09-09T08:01:05+00:00

fix($location): Use encodeUriQuery instead of escape

2011-09-08T21:00:59+00:00

Closes #492

fix(scenario): temporary fix for FF6

2011-09-08T21:00:59+00:00

https://bugzilla.mozilla.org/show_bug.cgi?id=684208

style: fix some missing semi-colons and spaces, typos

2011-09-08T21:00:59+00:00

refactor($route): remove some odd code and rename allowReload to forceReload

2011-09-08T21:00:59+00:00

fix(scenario): do not navigate if click event was cancelled

2011-09-08T21:00:59+00:00

This is jQuery incompatible hack.
But we were doing monkey patching there anyway...

`$(...).trigger('click')` returns an array of return values, so that scenario
runner knows, whether the event default action was cancelled.

Without this fix, scenario runner was doing navigation even if JS code called
`event.preventDefault()`.

Note, this does not work in FF6

doc($location): $location docs + using $location guide

2011-09-08T21:00:59+00:00

feat(scenario): browserTrigger returns false if preventDefault()

2011-09-08T21:00:59+00:00

https://developer.mozilla.org/en/DOM/element.dispatchEvent
dispatchEvent method returns false if at least one of the event handlers called
preventDefault(), true otherwise.

It's helpful when browserTrigger method returns this value, as we can assert,
whether the default operation was cancelled or not.

fix(docs): update docs to reflect new $location and fix e2e tests

2011-09-08T21:00:59+00:00