Changes to make Enyo suitable for Chrome packaged apps, as
inline enyo.bubbler script and its dependencies violated Content Security Policy(http://developer.chrome.com/extensions/contentSecurityPolicy.html)
Fixed a dumb mistake assuming arguments was an Array
Put enyo.bubbler back for backward compatibility
Added check for "unload" not being set on window if running under chrome extensions
Merge branch 'master' of https://github.com/vtomilin/enyo
Chrome packaged apps runtime does not expose chrome.extension, as it turns
out, which I used to determine whether the code has been deployed as an app.
Fixed
Merge branch 'master' of https://github.com/enyojs/enyo
ENYO-809: getParentNode modified

Enyo-DCO-1.0-Signed-off-by: Dave Freeman <Dave.Freeman@palm.com>

This change adds another possible rendering parent for enyo.Control's
getParentNode() method to return.  This is necessary for cases where the
kind's parentNode is null or its parent has no node, such as a
ScrollStrategy.
ENYO-809: getParentNode modified

Enyo-DCO-1.0-Signed-off-by: Dave Freeman <Dave.Freeman@palm.com>

This change adds another possible rendering parent for enyo.Control's
getParentNode() method to return.  This is necessary for cases where the
kind's parentNode is null or its parent has no node, such as a
ScrollStrategy.
ENYO-809: getParentNode modified

Enyo-DCO-1.0-Signed-off-by: Dave Freeman <Dave.Freeman@palm.com>

This change adds another possible rendering parent for enyo.Control's
getParentNode() method to return.  This is necessary for cases where the
kind's parentNode is null or its parent has no node, such as a
ScrollStrategy.
ENYO-809: getParentNode modified

Enyo-DCO-1.0-Signed-off-by: Dave Freeman <Dave.Freeman@palm.com>

This change adds another possible rendering parent for enyo.Control's
getParentNode() method to return.  This is necessary for cases where the
kind's parentNode is null or its parent has no node, such as a
ScrollStrategy.

Okay, I think I finally got it right this time :)
Merge pull request #143 from sugardave/ENYO-809

ENYO-809: getParentNode modified

Reviewed-By: Ben Combee (ben.combee@palm.com)
Improve enyo.Selection documentation to clairfy inData parameter usage.

Enyo-1.0-DCO-Signed-Off-By: Ben Combee (ben.combee@palm.com)
ENYO-544: use IE XDomainRequest for CORS

Enyo-DCO-1.0-Signed-off-by: Dave Freeman <dave.freeman@palm.com>

This changed up the getXMLHttpRequest method in xhr.js a bit.  It tries
to deal with IE requirements first before returning a new
XMLHttpRequest.  This requires passing the url to getXMLHttpRequest now.

Additonally, XDomainRequest does not have onreadystatechange, so
makeReadyStateHandler adds to onload in that case.
Add CONTRIBUTING md to repo so github will show "contribute" section at top of page

Enyo-DCO-1.0-Signed-Off-By: Ben Combee (ben.combee@palm.com)
ENYO-544: use IE XDomainRequest for CORS

Enyo-DCO-1.0-Signed-off-by: Dave Freeman <dave.freeman@palm.com>

This changed up the getXMLHttpRequest method in xhr.js a bit.  It tries
to deal with IE requirements first before returning a new
XMLHttpRequest.  This requires passing the url to getXMLHttpRequest now.

Additonally, XDomainRequest does not have onreadystatechange, so
makeReadyStateHandler adds to onload in that case.
moving inOrigin to a protected method of xhr
streamlined getXMLHttpRequest

now it is back to the original order of object returns after checking
for the special cases of needing to use XDomainRequest first
Merge branch 'master' of https://github.com/vtomilin/enyo into vtomilin-master

Conflicts:
	source/touch/TranslateScrollStrategy.js

Enyo-DCO-1.0-Signed-off-by: Ben Combee (ben.combee@palm.com)
Reviewed-By: Ben Combee (ben.combee@palm.com)
Merge branch 'ENYO-544' of https://github.com/sugardave/enyo-core-fixes into ENYO-544