| Age | Commit message (Collapse) | Author | 
 | 
$xhr header defaults are now exposed as $xhr.defaults.headers.common and
$xhr.default.headers.<httpmethod>. This allows applications to configure
their defaults as needed.
This commit doesn't allow headers to be set per request, only per
application. Per request change would require api change, which I tried
to avoid *for now*.
 | 
 | 
forgot to fix tests in 6aee2938a71c99fdd35639725c6900347999f658
 | 
 | 
 | 
 | 
 | 
 | 
Support new date format, specifically day of week/Month of year in string
e.g. {{ someDate | data:"EEE, MMM d, yyyy" }} -> "Wed, Jul 10, 2011"
Closes #396
 | 
 | 
 | 
 | 
 | 
 | 
Closes #399
 | 
 | 
8cad231 broke $eager services
Problem is that the injector.eager function is not invoked when a new scope
is created. Added a test to make sure service is eagerly instantiated.
Closes #403
 | 
 | 
 | 
 | 
The fix does not change any production code, we only need to ignore couple of attributes that IE7 should not display:
* value attribute for LI
* selected attribut for SELECT
Simplified condition in compiler test, this should have been part of f9f0905f4ad7b1d0bb9b606a6d25fb1f88354a78
 | 
 | 
Older IEs serialize html uppercased, but IE9 does not...
Would be better to expect case insensitive, unfortuntaly jasmine does not allow
to user regexps for throw expectations.
Closes #392
 | 
 | 
* moved scenario e2e tests in test/scenario/e2e folder
* remove $location test
 | 
 | 
markup.js.
Also added coresponding descriptions  live examples and tests for each directive to be displayed on the website.
Closes #351
 | 
 | 
This behavior was changed by e83465c362c53ac7451183a775456f3112262f6e
So this commit should have been part of e83465c362c53ac7451183a775456f3112262f6e
Also removed hiding and navigating to about:blank as it makes no sense now...
 | 
 | 
 | 
 | 
Closes #301
 | 
 | 
 | 
 | 
 | 
 | 
 | 
 | 
Closes #338
 | 
 | 
 | 
 | 
 | 
 | 
 | 
 | 
 | 
 | 
 | 
 | 
 | 
 | 
 | 
 | 
 | 
 | 
zeros.
 | 
 | 
Closes #237
 | 
 | 
Closes #207
 | 
 | 
Opera translates name colors to numbers (red -> #ff0000)
Other browsers like FF or Chrome translate number to rgb (#ff0000 -> rgb(255, 0, 0)
So avoiding colors in tests is probably the easiest solution...
 | 
 | 
+ unit tests
 | 
 | 
Stupid IE8 in compatibility mode or in IE7 mode returns true for `('onhashchange' in window)`, but does not support hashchange event.
Closes #353
 | 
 | 
 | 
 | 
As well as wasNotCalled(), wasCalledWith(), wasNotCalledWith()
 | 
 | 
See http://bugs.jquery.com/ticket/1450
 | 
 | 
find . -name "*.js" -print | xargs sed -Ei s/[[:space:]]*$//
 | 
 | 
Couple of changes into angular.scenario runner:
 - add autotest config (runs tests when document ready)
 - update ObjectModel (forwards events)
 - use only one ObjectModel instance for all outputters
 - expose error msg and line number in ObjectModel.Spec and ObjectModel.Step
 - fix generating spec.ids
 - fix 'html' output so that it does not mutate ObjectModel
Couple of changes into docs / generator:
 - rename copy -> copyTpl
 - move docs/static into docs/examples (to avoid conflict with jstd proxy)
Running all docs e2e tests:
========================================================
1/ compile angular-scenario, jstd-scenario-adapter
>> rake compile
2/ build docs
>> rake docs
3/ start jstd server
>> ./server-scenario.sh
4/ capture some browser
5/ run node server to serve static content
>> node ../lib/nodeserver/server.js
6/ run tests
>> ./test-scenario.sh
 | 
 | 
Sending Content-type header causes JSTD (Jetty) proxy to change GET methods into POST.
 | 
 | 
Removed angular.scenario.Application.checkUrlStatus_ method and these tests:
* should call error handler if status check fails
* should perform a HEAD request to verify file existence
* should call error handler if status code is less than 200
* should call error handler if status code is greater than 299
* should call error handler if status code is greater than 299
 | 
 | 
This is a combination of 4 commits:
* Fix some small typos, missing semi-colons, etc.
* Fix comment for angular.scenario.SpecRunner.run method
* Fixed some missing semi-colons in cookbook
* Fixed missing semi-colon in nodeserver/server.js
 | 
 | 
test for 9bd2c396
 | 
 | 
all unit tests now pass under IE9
 | 
 | 
 | 
 | 
apparently IE9 is one step closer to becoming a real browser by
treating xmlns-like ("foo:") prefixes in node names as part of the
node name.
fixes:
https://groups.google.com/forum/?lnk=srg#!topic/angular/TGdrV4GsL8U
 | 
 | 
succcess callbacks should be executed for status codes in the range
of <200,300).
 | 
 | 
 | 
 | 
can we agree to put more white space into our code?
I follow there rules for specs:
- 1 blank line between sections of nontrivial it block
- 2 blank lines between it blocks
- 2 blank lines between describe blocks
- 2 blank lines between beforeEach and afterEach
- no blank line between describe and the first child it
- no blank lines between two or more closing }); lines
 |