| Age | Commit message (Collapse) | Author |
|
|
|
windgets
These widgets are useless and only trigger extra $updateViews.
The only reason we had them was to support ng:change on these widgets,
but since there are no bindings present in these cases it doesn't make
sense to support ng:change here. It's likely just a leftover from
getangular.com
Breaking change: ng:change for input[button], input[submit], input[reset], input[image]
and button widgets is not supported any more
|
|
- add e2e tests
- refactor the example by removing clear button and simplifying the code
|
|
since we don't know if the error was due to a client error (4xx) or
server error (5xx), we leave the status code as undefined.
|
|
|
|
- must use binary reading when using read function in q-fs module
otherwise some unicode character may be garbled.
Closes #497
|
|
$xhr.error's first argument (request) has no callback property anymore,
it's called success now...
This breaking change was introduced by b5594a773a6f07dcba914aa385f92d3305285b24
|
|
- the end index for slice, if not specified, is default to the
end of the array it operates on.
|
|
- Speed improvements (about 4x on flush phase)
- Memory improvements (uses no function closures)
- Break $eval into $apply, $dispatch, $flush
- Introduced $watch and $observe
Breaks angular.equals() use === instead of ==
Breaks angular.scope() does not take parent as first argument
Breaks scope.$watch() takes scope as first argument
Breaks scope.$set(), scope.$get are removed
Breaks scope.$config is removed
Breaks $route.onChange callback has not "this" bounded
|
|
Minor documentation fixes. Should not be any code changes.
One test changed due to dependency on text in documentation.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Users often don't see Tutorial and go straight to crappy Dev Guide,
changing the order should help find them right content in the right
order.
|
|
|
|
|
|
|
|
|
|
The arrow is a hint that user won't navigate to a new page, but instead
the instructions will be displayed inline.
|
|
Closes #408
|
|
|
|
|
|
|
|
|
|
The previous implementation didn't handle situation when in css
something was hidden with a cascaded display:none rule and then we
wanted to show it.
Unfortunatelly our test doesn't test this scenario because it's too
complicated. :-/
|
|
jqLite doesn't support class selectors, can find only by tag name...
|
|
both numbers and currency need to be formatted using a generic pattern
which can be replaced for a different pattern when angular is working in
a non en-US locale
for now only en-US locale is supported, but that will change in the
future
|
|
|
|
Closes# 450
|
|
Closes #463
|
|
Closes #448
|
|
Closes #464
|
|
Closes #449
|
|
|
|
|
|
|
|
|
|
- fixed copyright overnship
- updated copyright years
- added @license tag so that closure compiler preserves the header
- added version number into headers (finally!)
|
|
- placeholders are replaced with actual angular versions when doing
rake compile
|
|
- re-write gendocs.js, reader.js and writer.js
- all calls are asynchronous
|
|
Generate a manifest file automatically by reading the directories.
|
|
- add support for full,long, medium, short datetime formats in en
Breaks MMMMM. now we don't support MMMMM anymore as old implementation differs
from Unicode Locale Data format we are following.
- removed support for fullDateTime and fullTime as it means too much
trouble with full timeZone names
- added docs for the new features
|
|
- If the third param of TzDate constructor is defined, toStirng will
just return this third parameter. Otherwise, toString will still
be treated as unimplemented method
|
|
|
|
This reverts commit 2428907259fa80ec3b1b4bfd85ea20028a9f4fa5.
We decided to revert this because it is not bullet proof. The issue is
that we can't reliably have both angular and non-angular code in charge
of the DOM. We could work around some issues here and there, but we
can't do it reliably, so it's better not to support DOM manipulation
that happens outside of angular. There is a good chance that once we
integrate with MDVs our possition will change, but until then our
position is that only angular or angular widgets/directives can change
change DOM that was compiled.
|
|
|