forattribute from Console's HTML templates. There is a bug in the WinJS runtime for Windows 8 apps that causes an error to be thrown incorrectly when certain element attributes used. [Ticket #2532792]
datasource-xmlschemanow forces input through the
Y.XMLparser. [Ticket #2532838]
event-move supports the -ms-touch-action property in IE10.
Nodes subscribing to events defined in event-move will have their
styles updated to
-ms-touch-action:none. It will be reset when
listeners are detached.
Changed onbeforeactivate feature test to account for Win 8 packaged Apps, which don't allow inline JS code in innerHTML.
Fixed Get issues, highlighted by IE10.
1) IE10 seems to interrupt JS execution, in the case of a 304'ing script to invoke the onLoad handler. If this happened inside the transaction execute loop, the transaction would terminate early (call onSuccess before all scripts were done), because the _waiting count would only reflect the number of scripts added to the DOM, when the loop was interrupted. Changed the logic so that we only finish a transaction when the expected number of requests are accounted for which seems reasonable in general.
Also wrapped the internal onLoad/onError callbacks in a setTimeout for IE10, so we're re-introducing asynchronicty for external onSuccess, etc. app code. We can take this out when/if the bug below gets fixed.
2) transaction._finish() would move on to the next transaction, before the current
transaction's onSuccess/Finish/End listeners were invoked, since the logic to move to
the next transaction was invoked before the
on listeners were invoked. This meant that
for all browsers, when issuing a CSS transaction followed by a JS transaction, the CSS
success callback wouldn't be invoked until the JS transaction was initiated.
3) Added user-agent to feature test for async support, because IE10 wasn't returning true for it. If IE10 ends up fixing the issue below by GA, we'll pull out the explicit ua test.
Get should work OK with IE10 now aside from one pending issue. If you issue 2 Get requests to the same 404ing script, IE10 doesn't call the success handler for the subsequent valid (200 etc.) request. This seems to be an IE10 issue, which we cannot control:
Fixed issue in Chrome where form submits with
upload: true were not working
properly. [Ticket #2531860]
empty() method to io-queue which clears out all requests waiting to be
sent. [Pull Request #282] [Julien Sanchez]
Add support for non-vendor-prefixed syle and CSS properties.
now supports IE10 and Opera.
Transition durations are now normalized from seconds to milliseconds before updating the node's style. Note: This does not affect the public API which still uses second-based duration times.
defaultButtonchanging by binding to the
defaultButtonChangeevent in WidgetButtons'
Last edited by ericf,