Tag: v1.3.6
-
docs($interval): correcting example code indentation
Bueno! Closes #10372
-
-
docs(contributing): correct push -f command
`git push -f` needs branch specification In all cases, please consult the git manpages before consulting angular's contributing guide when you need help with git, thx ^^ Closes #10356
-
docs(guide/controllers): Just a typo
Gingerbreak would break testing. :) Oh my gosh he's right, it totally w/ould. That is so embarrassing! Closes #10353
-
-
-
chore(travis): clean up browserstack/saucelabs scripts
vojtajina committedDec 4, 2014 -
chore(travis): enable both SauceLabs and BrowserStack
vojtajina committedDec 4, 2014 Setting env var `BROWSER_PROVIDER` to `browserstack` or `saucelabs` determines which browser provider will be used. This does not affect the build as all jobs are set to use SauceLabs. Switch to Karma with Socket.io 1.x, which solves some issues(*) with BS. Thus removing `config.transports` as it is not used anymore (Socket.io 1.x starts with polling and tries to upgrade if available). (*) folks from BS were fiddling with socket.io configuration to get it stable. See dhimil/karma@4c04011 This is not necessary with Socket.io 1.x.
-
-
docs(guide/forms): enhanced form examples to utilize $touched
The "Binding to form and control state" example now makes use of control states that were introduced in 1.3. For example, users are now informed of validation requirements upon clicking 'Save'. Closes #10066
-
fix(ngModelController): always use the most recent viewValue for vali…
…dation This fixes issues where a parser calls $setViewValue. This is a common strategy for manipulating the $viewValue while the user is entering data into an input field. When the $viewValue was changed inside the parser, the new viewValue would be committed, parsed and used for validation. The original parser however would run after that and pass the original (outdated) viewValue on to the validators, which could cause false positives, e.g. for minlength. Fixes #10126 Fixes #10299
-
docs(guide/migration): add info about change that could break isolate…
…d directive usage Closes #10236
-
feat($$jqLite): export jqLite as a private service
This makes it easy to use jqLite's nicer class API (compared to jQuery) in modules like ngAnimate.
-
fix(ngAnimate): do not use jQuery class API
caitp committedDec 4, 2014 -
-
-
fix($location): allow hash fragments with hashPrefix in hash-bang loc…
…ation urls Previously if there was a hash fragment but no hashPrefix we would throw an error. Now we assume that the hash-bang path is empty and that the hash is a valid fragment. This prevents unnecessary exceptions where we clear the hashBang path, say by navigating back to the base url, where the $browser leaves an empty hash symbol on the URL to ensure there is no browser reload. BREAKING CHANGE: We no longer throw an `ihshprfx` error if the URL after the base path contains only a hash fragment. Previously, if the base URL was `http://abc.com/base/` and the hashPrefix is `!` then trying to parse `http://abc.com/base/#some-fragment` would have thrown an error. Now we simply assume it is a normal fragment and that the path is empty, resulting `$location.absUrl() === "http://abc.com/base/#!/#some-fragment"`. This should not break any applications, but you can no longer rely on receiving the `ihshprfx` error for paths that have the syntax above. It is actually more similar to what currently happens for invalid extra paths anyway: If the base URL and hashPrfix are set up as above, then `http://abc.com/base/other/path` does not throw an error but just ignores the extra path: `http://abc.com/base`. Closes #9629 Closes #9635 Closes #10228 Closes #10308
-
fix($browser): prevent infinite digests when clearing the hash of a url
petebacondarwin committedNov 11, 2014
-
fix(inputs): ignoring input events in IE caused by placeholder change…
…s or focus/blur on inputs with placeholders Closes #9265
-
Removed a triling whitespace
-
docs(select): Updated ngOptions track by examples
Made the example shown consistent with the advice above it regarding not using `select as` and `track by` in the same comprehension expression. Also changed references to `trackexpr` to `track by` since `trackexpr` is not defined except in the examples. Added filter + track by example for ngOptions The documentation for ngRepeat includes such an example specifying the proper order for filters and and "track by" clauses in the comprehension expression, but these docs for ngOptions do not.
-
fix(parse): fix operators associativity
Make the operators `&&`, `==`, `!=`, `===`, `!==`, `<`, `>`, `<=`, `>=` follow Javascript left-to-right associativity
-
fix(orderBy): make object-to-primtiive behaviour work for objects wit…
…h null prototype
-
fix(orderBy): maintain order in array of objects when predicate is no…
caitp committedDec 3, 2014 …t provided In ES262, there are two properties which are used to get a primitive value from an Object: - valueOf() -- a method which returns a primitive value represented by the Object - toString() -- a method which returns a string value representing the Object. When comparing objects using relational operators, the abstract operation ToPrimitive(O, TypeHint) is used, which will use these methods to retrieve a value. This CL emulates the behaviour of ToPrimitive(), and ensures that no ordering occurs if the retrieved value is identical. This behaviour was previously used for Date objects, however it can be safely made generic as it applies to all objects. Closes #9566 Closes #9747 Closes #10311
-
Closes #10296
-
docs(guide/css-styling): form controls are not always input elements
People frequently write custom form controls using the `ngModel` directive, this just refactors the text to be more clear that this is possible (imho).