Skip to content
Permalink
Tag: v1.3.6
Commits on Dec 8, 2014
  1. docs($interval): correcting example code indentation

    saibotsivad authored and caitp committed Dec 8, 2014
    Bueno!
    
    Closes #10372
  2. chore(changelog): add test for addition of trailing newline

    gkalpak authored and caitp committed Oct 10, 2014
    Adds tests for the functionality added by #9550.
    
    Closes #10358
  3. docs(contributing): correct push -f command

    gregjhogan authored and caitp committed Dec 7, 2014
    `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
  4. docs(guide/controllers): Just a typo

    carusog authored and caitp committed Dec 6, 2014
    Gingerbreak would break testing. :)
    
    Oh my gosh he's right, it totally w/ould. That is so embarrassing!
    
    Closes #10353
  5. docs(ngView): remove multiple position: relative

    clarkduvall authored and pkozlowski-opensource committed Dec 8, 2014
    Closes #10363
Commits on Dec 6, 2014
  1. fix(http): preserve config object when resolving from cache

    shahata authored and pkozlowski-opensource committed Sep 11, 2014
    Fixes #9004
    Closes #9030
  2. chore(grunt): remove unused code

    vojtajina committed Dec 4, 2014
  3. chore(travis): enable both SauceLabs and BrowserStack

    vojtajina committed Dec 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.
Commits on Dec 5, 2014
  1. refactor(ngAria): remove local camelCase method

    cironunes authored and petebacondarwin committed Dec 5, 2014
    Closes #10338
    Closes #10337
  2. docs(compile): document $attrs.$normalize

    cironunes authored and caitp committed Dec 5, 2014
    Closes #10345
  3. docs(guide/forms): enhanced form examples to utilize $touched

    supersonicclay authored and Narretz committed Nov 14, 2014
    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
  4. fix(ngModelController): always use the most recent viewValue for vali…

    Narretz committed Dec 2, 2014
    …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
  5. docs(ie): remove fixes needed for IE8 since we don't support it now

    madskonradsen authored and petebacondarwin committed Dec 4, 2014
    Closes #10330
    Closes #10316
  6. docs(guide/migration): add info about change that could break isolate…

    petebacondarwin committed Dec 5, 2014
    …d directive usage
    
    Closes #10236
Commits on Dec 4, 2014
  1. feat($$jqLite): export jqLite as a private service

    caitp committed Dec 4, 2014
    This makes it easy to use jqLite's nicer class API (compared to jQuery) in modules
    like ngAnimate.
  2. fix(ngAnimate): do not use jQuery class API

    caitp committed Dec 4, 2014
    jQeury's class API causes problems with SVG elements --- using jqLite in all cases
    prevents issues.
    
    Closes #10024
    Closes #10329
  3. docs($animate): improve formatting of inline code

    btford committed Dec 4, 2014
  4. docs($location.ihshprfx): remove docs for unused error

    petebacondarwin committed Dec 4, 2014
  5. fix($location): allow hash fragments with hashPrefix in hash-bang loc…

    petebacondarwin committed Dec 3, 2014
    …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
  6. fix($browser): prevent infinite digests when clearing the hash of a url

    petebacondarwin committed Nov 11, 2014
    By using `location.hash` to update the current browser location when only
    the hash has changed, we prevent the browser from attempting to reload.
    
    Closes #9629
    Closes #9635
    Closes #10228
    Closes #10308
Commits on Dec 3, 2014
  1. fix(ngmodel): fixing many keys incorrectly marking inputs as dirty

    jbedard authored and caitp committed Oct 28, 2014
  2. fix(inputs): ignoring input events in IE caused by placeholder change…

    jbedard authored and caitp committed Sep 24, 2014
    …s or focus/blur on inputs with placeholders
    
    Closes #9265
  3. chore(docs): fix jscs error

    lgalfaso committed Dec 3, 2014
    Removed a triling whitespace
  4. docs(select): Updated ngOptions track by examples

    SteveShaffer authored and lgalfaso committed Nov 26, 2014
    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.
  5. docs($location): improve $location.hash() example

    whayler1 authored and pkozlowski-opensource committed Dec 2, 2014
    Closes #10300
  6. fix(ngMock): allow numeric timeouts in $httpBackend mock

    pkozlowski-opensource authored and lgalfaso committed Nov 23, 2014
    Fixes #4891
  7. fix(parse): fix operators associativity

    lgalfaso committed Nov 23, 2014
    Make the operators `&&`, `==`, `!=`, `===`, `!==`, `<`, `>`, `<=`, `>=`
    follow Javascript left-to-right associativity
  8. fix(orderBy): make object-to-primtiive behaviour work for objects wit…

    caitp committed Dec 3, 2014
    …h null prototype
  9. fix(orderBy): maintain order in array of objects when predicate is no…

    caitp committed Dec 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
  10. docs(ngTransclude): improve markup consistency

    hartz89 authored and pkozlowski-opensource committed Dec 2, 2014
    Closes #10298
  11. docs($compile): fix spelling

    darul75 authored and pkozlowski-opensource committed Dec 2, 2014
    Closes #10296
  12. test($interpolate): adding tests for watching $interpolate functions

    jbedard authored and pkozlowski-opensource committed Nov 19, 2014
    Closes #10119
  13. docs(guide/css-styling): form controls are not always input elements

    caitp committed Dec 2, 2014
    People frequently write custom form controls using the `ngModel` directive, this just
    refactors the text to be more clear that this is possible (imho).
Older
You can’t perform that action at this time.