Add Guard for invalid readyState in IE9 and IE10

IE9 and IE10 can get into a state where 

document.readyState === "interactive" // => true

even though the document is not yet ready. This happens
when a script tag is added dynamically to A dom (can
be detached fragment) and completes loading. I will look
through for the tests to add.
Support loaded readyState in IE9, IE10

loaded should still be safe so this should allow the check to work for
that case as well as requiring that IE9 and IE10 interactive are ignored.
Updating result of source
Update ready.min.js
Added component.json
correcting so global context is proper surrounding `this`

using same pattern as done in bonzo and other similar libs, making sure there's a proper `context` instead of just the bare `this`.
updating minified file as well.
Merge pull request #19 from getify/master

minor tweak to make the context binding be proper
Merge pull request #18 from jb55/component

Add component.json
Issue 17 - Add Guard for invalid readyState in IE9 and IE10
Fixed errors #17 and #21
Basically a clone of #17, didn't realize "hack ?" was an actual function call.
Merge pull request #21 from elachlan/master

Reroll: Add Guard for invalid readyState in IE9 and IE10
bump version
Merge branch 'patch-1' of github.com:webspinner/domready into webspinner-patch-1

Conflicts:
	ready.min.js
	src/ready.js
add MIT license file. closes #23
0.3.0
new domready deprecating old IE6,7,8 support
1.0.0
adds new copyright year in source