| Age | Commit message (Collapse) | Author | 
 | 
IE's window.eval doesn't execute in the global context, so we have to
use window.execScript instead which works like window.eval on normal
browsers. However execScript throws an exception when an empty string is
passed in, so I created a workaround with a workaround.
 | 
 | 
 | 
 | 
it looks like under certain circumstances the location service doesn't
propagate chages to window.loction. I'm disabling this test now, it is
passing on the master branch (0.10.0)
 | 
 | 
- buzz api keeps on throttling our requests which makes our build fail
  so I'm disabling the buzz demo e2e test
- the $xhr service jsonp test was modified to use jsonp on angularjs.org
  instead of buzz api for the same reason as mentioned above
 | 
 | 
the max size for safari cookies has changed sligtly so I had to adjust
the test to make cookie creation fail on this browser
 | 
 | 
- tutorial section of docs fails to render properly as
doc:tutorial-instructions widget uses deprecated show and hide methods
of jQlite.
 | 
 | 
 | 
 | 
 | 
 | 
 | 
 | 
 | 
 | 
$new can't be used for creation of temporary scopes because it registers
an onEval listener that doesn't go away and keeps the scope around, we
must use inherit(scope) instead to avoid this issue.
The issue does not apply to the master branch with the new scope which
has a scope descructor to clean up this mess.
 | 
 | 
 | 
 | 
In order to avoid unnecesary route reloads when just hashSearch part
of the url changes, it is now possible to disable this behavior by
setting reloadOnSearch param of the route declaration to false.
Closes #354
 | 
 | 
all $xhr*, $resource and related mocks now have access to headers from
their callbacks
 | 
 | 
two arguments
 | 
 | 
 | 
 | 
Change doc_widget.js to:
- render "edit in jsfiddle" button next to all examples
- make opt out certain examples by adding jsfiddle="false" attribute to
  doc:source element
 | 
 | 
it turns out that even with our tricks, jqLite#show is not usable in
practice and definitely not on par with jQuery. so rather than
introducing half-baked apis which introduce issues, I'm removing them.
I also removed show/hide uses from docs, since they are not needed.
Breaks jqLite.hide/jqLite.show which are no longer available.
 | 
 | 
 | 
 | 
Closes #508
 | 
 | 
 | 
 | 
This was causing to show up the "$browser" twice in the menu.
 | 
 | 
Closes #506
 | 
 | 
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
 | 
 | 
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...
 |