<feed xmlns='http://www.w3.org/2005/Atom'>
<title>angular.js/test/ngScenario, branch v1.2.10</title>
<subtitle></subtitle>
<link rel='alternate' type='text/html' href='https://git.teddywing.com/fork/angular.js/'/>
<entry>
<title>perf(jqLite): implement and use the `empty` method in place of `html(‘’)`</title>
<updated>2013-12-13T10:07:11+00:00</updated>
<author>
<name>Michał Gołębiowski</name>
</author>
<published>2013-10-16T13:15:21+00:00</published>
<link rel='alternate' type='text/html' href='https://git.teddywing.com/fork/angular.js/commit/?id=3410f65e790a81d457b4f4601a1e760a6f8ede5e'/>
<id>3410f65e790a81d457b4f4601a1e760a6f8ede5e</id>
<content type='text'>
jQuery's elem.html('') is way slower than elem.empty(). As clearing
element contents happens quite often in certain scenarios, switching
to using .empty() provides a significant performance boost when using
Angular with jQuery.

Closes #4457
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
jQuery's elem.html('') is way slower than elem.empty(). As clearing
element contents happens quite often in certain scenarios, switching
to using .empty() provides a significant performance boost when using
Angular with jQuery.

Closes #4457
</pre>
</div>
</content>
</entry>
<entry>
<title>test($browser): correct false positive in ApplicationSpec.js</title>
<updated>2013-09-11T21:19:24+00:00</updated>
<author>
<name>Woody Peterson</name>
</author>
<published>2013-09-04T15:01:43+00:00</published>
<link rel='alternate' type='text/html' href='https://git.teddywing.com/fork/angular.js/commit/?id=64e7b7774e3d0cb2e36efe00d550c7e53ec7efa5'/>
<id>64e7b7774e3d0cb2e36efe00d550c7e53ec7efa5</id>
<content type='text'>
Previously, the check that Application should return a new $window and
$document had the arguments reversed in the first call to navigateTo;
thus, the subsequent check of inequality of $window and $document in the
next navigateTo call would always pass.

This corrects the argument order, which makes this test not succeptible
to false positives.
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
Previously, the check that Application should return a new $window and
$document had the arguments reversed in the first call to navigateTo;
thus, the subsequent check of inequality of $window and $document in the
next navigateTo call would always pass.

This corrects the argument order, which makes this test not succeptible
to false positives.
</pre>
</div>
</content>
</entry>
<entry>
<title>feat(scenario): expose jQuery for usage outside of angular scenario</title>
<updated>2013-07-31T22:50:12+00:00</updated>
<author>
<name>Andreas Marek</name>
</author>
<published>2013-07-24T19:20:39+00:00</published>
<link rel='alternate' type='text/html' href='https://git.teddywing.com/fork/angular.js/commit/?id=3fdbe81a337c39027929c415e719493755cd8583'/>
<id>3fdbe81a337c39027929c415e719493755cd8583</id>
<content type='text'>
The global jQuery reference is removed by angular scenario and only a local scoped reference is kept. To make jQuery available for other code, a new reference angular.scenario.jQuery is added.
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
The global jQuery reference is removed by angular scenario and only a local scoped reference is kept. To make jQuery available for other code, a new reference angular.scenario.jQuery is added.
</pre>
</div>
</content>
</entry>
<entry>
<title>fix(ngScenario): select().option(val) should prefer exact value match</title>
<updated>2013-07-12T09:05:23+00:00</updated>
<author>
<name>Stephen Merity</name>
</author>
<published>2013-06-03T08:09:36+00:00</published>
<link rel='alternate' type='text/html' href='https://git.teddywing.com/fork/angular.js/commit/?id=22a9b1ac07f98d07e1e5d71ce961411b5fa9b42d'/>
<id>22a9b1ac07f98d07e1e5d71ce961411b5fa9b42d</id>
<content type='text'>
With select(...).option(val) it previously would select the first node
which contains the value, even if an exact match was available.
This fix prefers exact matches if available, otherwise it reverts
to the previous 'contains' behaviour for backwards compatibility.

Closes #2856
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
With select(...).option(val) it previously would select the first node
which contains the value, even if an exact match was available.
This fix prefers exact matches if available, otherwise it reverts
to the previous 'contains' behaviour for backwards compatibility.

Closes #2856
</pre>
</div>
</content>
</entry>
<entry>
<title>chore: remove jstd leftovers</title>
<updated>2013-06-28T18:43:38+00:00</updated>
<author>
<name>Vojta Jina</name>
</author>
<published>2013-06-25T18:24:02+00:00</published>
<link rel='alternate' type='text/html' href='https://git.teddywing.com/fork/angular.js/commit/?id=89efb12ed852070a93777c5ff0ed3f9bc822bdf0'/>
<id>89efb12ed852070a93777c5ff0ed3f9bc822bdf0</id>
<content type='text'>
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
</pre>
</div>
</content>
</entry>
<entry>
<title>feat(jqLite): switch bind/unbind to more recent jQuery on/off</title>
<updated>2013-06-19T19:53:24+00:00</updated>
<author>
<name>Michał Gołębiowski</name>
</author>
<published>2013-06-19T19:52:50+00:00</published>
<link rel='alternate' type='text/html' href='https://git.teddywing.com/fork/angular.js/commit/?id=f1b94b4b599ab701bc75b55bbbbb73c5ef329a93'/>
<id>f1b94b4b599ab701bc75b55bbbbb73c5ef329a93</id>
<content type='text'>
jQuery switched to a completely new event binding implementation as of
1.7.0, centering around on/off methods instead of previous bind/unbind.
This patch makes jqLite match this implementation while still supporting
previous bind/unbind methods.
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
jQuery switched to a completely new event binding implementation as of
1.7.0, centering around on/off methods instead of previous bind/unbind.
This patch makes jqLite match this implementation while still supporting
previous bind/unbind methods.
</pre>
</div>
</content>
</entry>
<entry>
<title>feat(scenario): adds mousedown and mouseup event triggers to scenario</title>
<updated>2013-05-14T19:50:36+00:00</updated>
<author>
<name>Andreas Marek</name>
</author>
<published>2013-05-06T08:20:15+00:00</published>
<link rel='alternate' type='text/html' href='https://git.teddywing.com/fork/angular.js/commit/?id=629fb37351ce5778a40a8bc8cd7c1385b382ce75'/>
<id>629fb37351ce5778a40a8bc8cd7c1385b382ce75</id>
<content type='text'>
Added mousedown and mouseup event triggers to scenadio dsl 'element' expression.
Added mousedown and mouseup to the custom jquery trigger method to generate real events.
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
Added mousedown and mouseup event triggers to scenadio dsl 'element' expression.
Added mousedown and mouseup to the custom jquery trigger method to generate real events.
</pre>
</div>
</content>
</entry>
<entry>
<title>feat(Scenario): autodisable animations when running e2e tests</title>
<updated>2013-04-04T00:40:15+00:00</updated>
<author>
<name>Igor Minar</name>
</author>
<published>2013-04-03T21:36:57+00:00</published>
<link rel='alternate' type='text/html' href='https://git.teddywing.com/fork/angular.js/commit/?id=fec4ef38815340e8e5a6b65fd6c08f5c74e701d8'/>
<id>fec4ef38815340e8e5a6b65fd6c08f5c74e701d8</id>
<content type='text'>
animations cause the dom to contain elements that have been removed
from the model but are being animated out.

we could teach the e2e runner to wait for animations but that would
make all tests slower. it should be quite safe to just disable
animations automatically when the app is running via the e2e test
runner.

this change disables only css animations. we should make additional
change that disables js animations as well, but since we don't need
this right now I'm punting on it.
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
animations cause the dom to contain elements that have been removed
from the model but are being animated out.

we could teach the e2e runner to wait for animations but that would
make all tests slower. it should be quite safe to just disable
animations automatically when the app is running via the e2e test
runner.

this change disables only css animations. we should make additional
change that disables js animations as well, but since we don't need
this right now I'm punting on it.
</pre>
</div>
</content>
</entry>
<entry>
<title>fix(scenario): include error messages in XML output</title>
<updated>2013-02-07T12:09:52+00:00</updated>
<author>
<name>Julie</name>
</author>
<published>2012-10-09T18:13:26+00:00</published>
<link rel='alternate' type='text/html' href='https://git.teddywing.com/fork/angular.js/commit/?id=d46fe3c23fa269dcc10249148f2af14f3db6b066'/>
<id>d46fe3c23fa269dcc10249148f2af14f3db6b066</id>
<content type='text'>
Fix the XML output of scenario tests so that it properly includes error
messages from failing specs.
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
Fix the XML output of scenario tests so that it properly includes error
messages from failing specs.
</pre>
</div>
</content>
</entry>
<entry>
<title>feat(scenario): add mouseover method to the ngScenario dsl</title>
<updated>2013-01-19T05:24:57+00:00</updated>
<author>
<name>Pedro Del Gallego</name>
</author>
<published>2013-01-19T05:24:07+00:00</published>
<link rel='alternate' type='text/html' href='https://git.teddywing.com/fork/angular.js/commit/?id=2f437e89781cb2b449abb685e36b26ca1cf0fff5'/>
<id>2f437e89781cb2b449abb685e36b26ca1cf0fff5</id>
<content type='text'>
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
</pre>
</div>
</content>
</entry>
</feed>
