angular.js/lib/grunt, branch v1.2.11 feat(build): add a grunt test for running protractor tests extracted from the docs 2014-01-10T01:21:46+00:00 Julie 2014-01-07T19:51:32+00:00 2ed4ad55022f6e5519617a3797649fe1e68f3734 






chore(build): automate cutting a release, publishing to bower and to code.angular.js
2013-12-13T20:51:13+00:00

Tobias Bosch

2013-12-13T20:49:42+00:00

8c10db384727643265b1550543011d3193dfe557












chore(travis): switch back to SauceLabs
2013-12-03T23:49:19+00:00

Vojta Jina

2013-12-03T20:15:36+00:00

6127528b5008a507966c7f1a1030db27ca2fbc0b

I think we are pretty close to be able to use both.

The xhr-polling seems to be pretty stable, but I'm having problems with multiple SSH tunnels (on BS), so let's try to switch back to SL.





I think we are pretty close to be able to use both.

The xhr-polling seems to be pretty stable, but I'm having problems with multiple SSH tunnels (on BS), so let's try to switch back to SL.







chore(travis): use different port numbers per build
2013-12-03T23:49:18+00:00

Vojta Jina

2013-12-03T17:58:30+00:00

84187b6d94179edf04512038f68c14f34a8e6219

We can't establish multiple SSH tunnels for the same port (for BrowserStack).
This makes it possible to run multiple parallel builds using BrowserStack.





We can't establish multiple SSH tunnels for the same port (for BrowserStack).
This makes it possible to run multiple parallel builds using BrowserStack.







fix(minErr): remove references to internals APIs
2013-11-14T23:00:53+00:00

Vojta Jina

2013-11-14T22:18:55+00:00

94764ee08910726db1db7a1101c3001500306dea

So that we can use minErr with angular-loader, before full angular is loaded.

This also fixes replacing the version during the build.





So that we can use minErr with angular-loader, before full angular is loaded.

This also fixes replacing the version during the build.







fix(grunt): Fix NG_VERSION_MINOR typo
2013-11-12T21:05:27+00:00

Andrei Korzhevskii

2013-11-09T15:19:30+00:00

fa82a31fa6c7ded00c8b7b0a62ba05d409fcbf00












chore(Grunt): use the latest Content-Security-Policy header in csp mode
2013-10-22T22:21:24+00:00

Igor Minar

2013-10-22T22:05:40+00:00

2d8d6dd192322a60a3dbad7485d1395a161b3130












fix: don't inline css in csp mode.
2013-10-22T22:21:23+00:00

tigbro

2013-10-14T19:06:26+00:00

a86cf20e67202d614bbcaf038c5e04db94483256

Also add `angular-csp.css` to the resulting build.





Also add `angular-csp.css` to the resulting build.







fix(csp): fix csp auto-detection and stylesheet injection
2013-10-19T00:33:53+00:00

Igor Minar

2013-10-15T22:00:22+00:00

08f376f2ea3d3bb384f10e3c01f7d48ed21ce351

When we refactored , we broke the csp mode because the previous implementation
relied on the fact that it was ok to lazy initialize the .csp property, this
is not the case any more.

Besides, we need to know about csp mode during bootstrap and avoid injecting the
stylesheet when csp is active, so I refactored the code to fix both issues.

PR #4411 will follow up on this commit and add more improvements.

Closes #917
Closes #2963
Closes #4394
Closes #4444

BREAKING CHANGE: triggering ngCsp directive via `ng:csp` attribute is not
supported any more. Please use data-ng-csp instead.





When we refactored , we broke the csp mode because the previous implementation
relied on the fact that it was ok to lazy initialize the .csp property, this
is not the case any more.

Besides, we need to know about csp mode during bootstrap and avoid injecting the
stylesheet when csp is active, so I refactored the code to fix both issues.

PR #4411 will follow up on this commit and add more improvements.

Closes #917
Closes #2963
Closes #4394
Closes #4444

BREAKING CHANGE: triggering ngCsp directive via `ng:csp` attribute is not
supported any more. Please use data-ng-csp instead.







chore(grunt): switch to the new //# sourceMappingURL pragma
2013-10-01T19:30:50+00:00

Michał Gołębiowski

2013-09-24T17:52:20+00:00

936101041a9a1f1cf9fecf6b5fcfae206cd15424

All browsers except from Chrome implemented both the old
"//@ sourceMappingURL" and the new "//# sourceMappingURL" pragmas
in the same version so the only reason to keep the old one was Chrome.
However, Chrome 29, i.e. current stable version already supports
the new pragma so there's no need to wait any longer.





All browsers except from Chrome implemented both the old
"//@ sourceMappingURL" and the new "//# sourceMappingURL" pragmas
in the same version so the only reason to keep the old one was Chrome.
However, Chrome 29, i.e. current stable version already supports
the new pragma so there's no need to wait any longer.