angular.js/src/scenario, branch v0.10.2

fix(scenario): workaround for FF6 dispatchEvent issue #684208

2011-09-26T21:51:54+00:00

Revert "fix(scenario): temporary fix for FF6"

2011-09-26T21:51:54+00:00

This reverts commit aac68bf2ba2dcdf0b22fa4f15ea49672cb06328d.

fix(scenarioRunner): navigateTo should use prop('contentWindow')

2011-09-16T00:44:35+00:00

... instead of attr('contentWindow')

feat(scenarioRunner): adding support for element().prop()

2011-09-16T00:44:34+00:00

since jQuery 1.6.4 attr() focuses only on work with element attributes and doesn't deal well with element properties, so adding prop() support is required for getting many e2e tests to pass after upgrading the runner to jQuery 1.6.4.

fix(scenario dsl): jQuery getters must have no value

2011-09-16T00:44:31+00:00

jQuery now requires getter methods to have no value at all -
they do arguments.length check to identify getters vs setters.

feat (jquery): upgrade everything to jQuery 1.6.4

2011-09-16T00:44:27+00:00

Closes #556

fix(scenario): temporary fix for FF6

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

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

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

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.

style(*): remove extra semicolons

2011-08-15T07:21:02+00:00