| Age | Commit message (Collapse) | Author | 
|---|
|  |  | 
|  | `angular.Array.limitTo`'s  result should not exceed original input array size
Closes #571 | 
|  | is no longer auto-published on the root scope, so we need to publish
it via a controller | 
|  |  | 
|  | this fix is needed for Firefox or other browsers that strictly follow
dom/css spec which states that element.style should make properties
available in camelCased form.
Closes #569 | 
|  |  | 
|  | defaults definned per action should take precedence over defaults
defined for the whole resource.
This is potentialy a BREAKING CHANGE in case someone relied on the buggy
behavior. | 
|  | using appcache while running e2e tests was causing the following
problems:
- Safari would occasionally reload the app (as a result of the appcache
  refresh) during the angular.validator.asychronous test, which would
  result in test failure and false positivy.
- Firefox6 would run the tests very slowly, disabling the cache resolved
  the latency issues
- Sometimes tests would run with stale code pulled from cache, which
  would result in flaky tests. | 
|  |  | 
|  | This reverts commit aac68bf2ba2dcdf0b22fa4f15ea49672cb06328d. | 
|  | - Configure our docs app to use new $location with html5 history api!
- Update simple node web server to serve index.html for all links
  (rewritting).
- Update .htaccess file to serve index.html for all links (rewritting).
- At runtime determine the base href path and attach it to the DOM. We
  needed the absolute URL to get all browsers to work well.
- Because of the above, we also need to dynamically determine all needed
  js/css resources and add them to the DOM. This was needed because FF6
  would eagerly fetch resources with wrong URL since the base element is
  added to the dom at runtime.
- All content html files were moved to the partials directory, because
  with the new html5 urls it was impossible to tell if request for
  http://domain/api/angular.filter.html was an html5 url for the html
  filter doc page, or an xhr/appcache request for the content html file
  for the html filter.
f | 
|  |  | 
|  |  | 
|  | Because of changes in jQuery, we need to use element().prop() instead of element().attr() to retrieve className and other element properties.
Additionally all attribute selectors (e.g. input[name=value]) must have value quoted if it contains dots ("."). | 
|  | ... instead of attr('contentWindow') | 
|  | since jQuery 1.6.4 attr() focuses only on work with element attributes and doesn't deal well with element properties, so adding prop() support is required for getting many e2e tests to pass after upgrading the runner to jQuery 1.6.4. | 
|  |  | 
|  | It appears that this whole time all IE8 unit tests ran only with jqLite. Due to a weird bug in IE[1], we never overwrote jqLite implementation with jQuery, so the tests ran with our jqLite instead.
This affected only IE8 (and likely older) and only in unit testing mode. angular.js - the built artifact binds to jQuery just find.
[1] https://plus.google.com/104744871076396904202/posts/Kqjuj6RSbbT | 
|  | for special attrs like 'checked' or 'multiple', jquery now returns the name or undedefined.
e.g. foo.attr('checked') => 'checked' || undefined
The solution is a combination of updating our tests as well as switching
over to prop() instead which properly returns true/false | 
|  | link rewriting used in html5 mode on legacy browsers binds to document.onClick - we need to destroy this listener after each test to prevent test collisions (global state is evil). | 
|  | jQuery now requires getter methods to have no value at all -
they do arguments.length check to identify getters vs setters. | 
|  | Contains 3 fixes:
- the internal model was by mistake using "checked" property instead of
  "selected"
- use jqLite.prop() to set 'selected' property
- added inChangeEvent check - we should not interfere with the browser
  selecting elements when not necessary | 
|  | since jQuery 1.6.4 prop() became very important because attr() does't have access to certain properties any more (e.g. className), so I'm adding it to jqLite as well so that jqLite preserves the feature-set it had before the jQuery upgrade. | 
|  |  | 
|  | supports these invocation types:
- foo.unbind();
- foo.unbind('eventType');
- foo.unbind('eventType', fn);
more info: http://api.jquery.com/unbind/ | 
|  | The behavior of attr() getter and setter changed in jQuery 1.6 and now they treat element properties and attributes as two different things, but in order to not break everyone there is a partial backwards compatibility for checking and updating element properties as well. see http://api.jquery.com/prop/ for more info. | 
|  | foo.css('bogus', 'value')
foo.css('bogus') => null
so I had to change all tests to use valid css rules | 
|  | since jQuery 1.6 'class' is not treated specially, so we have to revert this fix and use className in tests instead | 
|  | Closes #556 | 
|  |  | 
|  |  | 
|  | - move all script load order into angularFiles.js
- rakefile and angular-bootstrap.js use angularFiles.js to get script orders
- gen_jstd_configs.js uses angularFiles.js to generate various jstd config files
- run gen_jstd_configs.js whenever we run server.sh
Closes #470 | 
|  |  | 
|  |  | 
|  |  | 
|  | Closes #492 | 
|  | https://bugzilla.mozilla.org/show_bug.cgi?id=684208 | 
|  |  | 
|  |  | 
|  | This is jQuery incompatible hack.
But we were doing monkey patching there anyway...
`$(...).trigger('click')` returns an array of return values, so that scenario
runner knows, whether the event default action was cancelled.
Without this fix, scenario runner was doing navigation even if JS code called
`event.preventDefault()`.
Note, this does not work in FF6 | 
|  |  | 
|  | https://developer.mozilla.org/en/DOM/element.dispatchEvent
dispatchEvent method returns false if at least one of the event handlers called
preventDefault(), true otherwise.
It's helpful when browserTrigger method returns this value, as we can assert,
whether the default operation was cancelled or not. | 
|  |  | 
|  | * update $route to reflect new $location
* add some more unit tests to $route
* fix some other failing unit tests
* redirect overrides the url now
Breaks $route custom redirect fn has only 3 params now | 
|  | See documentation of $location for more info
Breaks $location has no properties, only get/set methods
Closes #168
Closes #146
Closes #281
Closes #234 | 
|  | Chrome's Event has defaultPrevented property, but other browsers haven't.
This is workaround for other browsers - same as jQuery. | 
|  | This method abstracts <base href="" /> in document.head - returns the value.
If absolute href set, it converts the href to relative. | 
|  | This only extracts our 'hashchange' event and html5 history api detection from
$browser.
Closes #400 | 
|  |  | 
|  | This is just basic implementation of $browser.url, $browser.onUrlChange methods:
$browser.url() - returns current location.href
$browser.url('/new') - set url to /new
If supported, history.pushState is used, location.href property otherwise.
$browser.url('/new', true) - replace current url with /new
If supported, history.replaceState is used, location.replace otherwise.
$browser.onUrlChange is only fired when url is changed from the browser:
- user types into address bar
- user clicks on back/forward button
- user clicks on link
It's not fired when url is changed using $browser.url()
Breaks Removed $browser.setUrl(), $browser.getUrl(), use $browser.url()
Breaks Removed $browser.onHashChange(), use $browser.onUrlChange() |