| Age | Commit message (Collapse) | Author | 
|---|
|  | Closes #6406 | 
|  | Currently there is only a minimal test spec in place. But this will now
be run as part of the test tasks. | 
|  | Before we were simply sending the current location, but multiple URLs map
to the same document.
Now, we use the canonical path of the current document if available and
fall back to the $location path otherwise.
Includes tests!!
Closes #6402 | 
|  | Fixes #6193
Closes #6226 | 
|  | browser
Use the multiConfiguration ability of Protractor to start tests on multiple browsers
from the same travis cell. Group tests by type (jquery, jqlite, or docs tests) instead
of by browser. Turn on tests for jQuery. | 
|  | Apparently some example files were referenced in angularFiles.js, and this was missed when
2f4513339337bb8aa6c9dfe1191d169b4fc57999 was checked in. This cleans it up.
Closes #6405 | 
|  | Before this fix, search queries in hashbang mode were ignored if the hash was not present in the
url. This patch corrects this by ensuring that the search query is available to be parsed by
urlResolve when the hashbang is not present.
Closes #5964 | 
|  | In browsers where HTML5 constraint validation is (partially) implemented, an invalid number
entered into an input[type=number] (for example) input element would be visible to the
script context as the empty string. When the required or ngRequired attributes are not used,
this results in the invalid state of the input being ignored and considered valid.
To address this, a validator which considers the state of the HTML5 ValidityState object is
used when available.
Closes #4293
Closes #2144
Closes #4857
Closes #5120
Closes #4945
Closes #5500
Closes #5944 | 
|  | Complimentary change to match changed $parse behaviour. | 
|  | There are always going to be false positives here, unfortunately. But
testing different properties will hopefully reduce the number of false
positives in a meaningful way, without harming performance too much.
Closes #4805
Closes #5675 | 
|  | This change makes the ngHref directive useful for SVGAElements by having it bind
to the xlink:href attribute rather than the href attribute.
Closes #5904 | 
|  | Closes #6342 | 
|  | Fixes #5985
Closes #6401 | 
|  | Let these poor scripts retire, goodness.
Closes #6398
Closes #3310 | 
|  |  | 
|  | Closes #6366 | 
|  | Closes #6389 | 
|  | Closes #6388 | 
|  | Closes #6387 | 
|  | Closes #6386 | 
|  | Closes #6385 | 
|  | Closes #6384 | 
|  | Closes #6383 | 
|  | Closes #6382 | 
|  | Closes #6381 | 
|  | Update to the latest dgeni-packages, which supports multiple
deployment environments for the examples.
Add a jQuery deployment environment for the examples.
Currently, the target of the runnable example iframe always points
to the default deployment environment, not to the environment under
which the main app is running.
Closes #6361 | 
|  | marked has an existing bug where links ending with a ')' will not be parsed correctly. The workaround
is to use a shortened URL. The original URL that is being replaced by this commit is
http://en.wikipedia.org/wiki/Minification_(programming) .
Closes #6377 | 
|  | and lower
Text specifies "polyfill JSON.stringify for IE7 and below" conditional comment for loading the
polyfill was "lte IE 8".
Closes #6227 | 
|  | Switched from this to $scope. It's confusing using $scope and this interchangeably.
Closes #6375 | 
|  | bindings
More description of "&" bindings, the fact that they trigger evaluation of expressions in the
original scope's context.
Closes #6255 | 
|  | IE has issues with this, it's good to make a note of this.
Closes #6329 | 
|  | Closes #6353 | 
|  | I have been looking around and was not able to find any informations on how to clear the $interval
but reading the source code, sharing is caring!
Closes #6367 | 
|  |  | 
|  | This got missed in the doc migration: When there is an error in an
Angular app, extra information is placed in the URL, which can be used
by the docs application to display a more useful message.
This fix adds that back in.  The error message templates are extracted
by the minerr tool during build and put into the errors.json file. The
errors-doc processor will load this up and attach these message templates
to the error docs.
The display of these templates was already in place, via the errorDisplay
directive in docs/app/js/errors.js.
(Also, moved the error.template.html file into the angular.js repository
from the dgeni-packages repository as this is specific to the angular.js
project and all the other error related stuff is in here.
Finally, also, added an e2e test that checks that minerr formatted
messages are displayed correctly.
Closes #6363 | 
|  |  | 
|  | Closes #6308 | 
|  |  | 
|  |  | 
|  | Closes #6219 | 
|  |  | 
|  |  | 
|  | Closes #6345
Somebody accidentally padded a list with one-too-many indentations, which caused the actual documentation page to render incorrectly. This should fix it. | 
|  |  | 
|  |  | 
|  | Closes #6331
Closes #6332 | 
|  | Building the G3 commits occupies a lot of time, and these branches have
already been tested.
Closes #6328 | 
|  | Oops. | 
|  | document, as in jQuery
This is a very tiny change to make behaviour consistent with jQuery.
Closes #6320
Closes #6323 | 
|  | Closes #6324. |