aboutsummaryrefslogtreecommitdiffstats
path: root/src/ng/sniffer.js
AgeCommit message (Collapse)Author
2013-05-08feat($sniffer): Add support for supportsAnimations flag for detecting CSS ↵Matias Niemelä
Animations browser support
2013-04-08fix($sniffer): $sniffer to support non-vendor prefixesMatias Niemelä
2013-04-02feat(ngAnimate): add support for animationMisko Hevery
2012-11-15fix(CSP): update to the latest CSP apiIgor Minar
window.SecurityPolicy.isActive() is now window.securityPolicy.isActive since this is available only in Chrome Canary which has already been updated, we can safely make this change without worrying about backwards compatilibty. Closes #1577
2012-08-10feat($sniffer): auto detect CSP modeVojta Jina
Chrome Canary now has CSP with apis that allow auto-detection. This change will turn on CSP mode automatically when we detect its presence. https://dvcs.w3.org/hg/content-security-policy/raw-file/tip/csp-specification.dev.html#script-interfaces--experimental
2012-06-12docs(*): simplify doc urlsIgor Minar
we now have two types of namespaces: - true namespace: angular.* - used for all global apis - virtual namespace: ng.*, ngMock.*, ... - used for all DI modules the virual namespaces have services under the second namespace level (e.g. ng.) and filters and directives prefixed with filter: and directive: respectively (e.g. ng.filter:orderBy, ng.directive:ngRepeat) this simplifies urls and makes them a lot shorter while still avoiding name collisions
2012-05-14fix($sniffer): report history false on Android < 4Vojta Jina
Android has history.pushState, but it does not update the location correctly: http://code.google.com/p/android/issues/detail?id=17471 Closes #904
2012-05-06fix(ngModel): use keydown/change events on IE9 instead of inputIgor Minar
On IE9 the input event is not fired when backspace or delete key are pressed or when cut is performed. This makes listening on the input event unreliable and therefore it's better for us to just use keydown/change events instead. Closes #879
2012-04-27feat($parse): CSP compatibilityIgor Minar
CSP (content security policy) forbids apps to use eval or Function(string) generated functions (among other things). For us to be compatible, we just need to implement the "getterFn" in $parse without violating any of these restrictions. We currently use Function(string) generated functions as a speed optimization. With this change, it will be possible to opt into the CSP compatible mode using the ngCsp directive. When this mode is on Angular will evaluate all expressions up to 30% slower than in non-CSP mode, but no security violations will be raised. In order to use this feature put ngCsp directive on the root element of the application. For example: <!doctype html> <html ng-app ng-csp> ... ... </html> Closes #893
2012-04-03feat($sniffer): add hasEvent method for sniffing eventsVojta Jina
Skip changelog
2012-03-28chore(module): move files around in preparation for more modulesMisko Hevery