adding deprecation warnings the right way for attributes and setter
Upgrading html5shiv to 3.7.2
Added IE8 Support section to can.Component docs. Fixes #926
Updating can.Component IE8 message
fixes bugs with docs
Merge pull request #972 from bitovi/mustache-doc-fixes

fixes bugs with docs
Merge pull request #971 from bitovi/926-docs-component-ie8-support

926 docs component ie8 support
Fixing unformatted code block in Recipe guide
Misspelling in stache docs - differences from mustache

Just fixes a typo, should be Differences.
#975 add warning when component fails silently
jshint fix
better warning text
adding tests for can.route.map
added can parameter

`can.view.parser` is set at the end of the file. The dependency `can` is
not imported, this causes issues during AMD optimization, because the
reference can at that point doesn't exist through `window.can`, as it
does in the browser.
Failing test for custom element namespace in IE8

This adds a failing test to the issue where custom elements that have
been registered with can.view.tag are being rendered in IE8 with a
preceding `:` because they lose their namespace. This problem does not
occur in Mustache.

The issue is likely caused by stache using cloneNode internally. There
are various issues with cloneNode that are solved by jQuery and HTML5
Shiv includes a note in their readme that they do not address the
cloneNode problem.
added can parameter as import to stache

Several properties are set on `can` in the file. The dependency `can` is
not imported, this causes issues during AMD optimization, because the
reference `can` at that point doesn't exist through `window.can`, as it
does in the browser.
fixed tab whitespace
changed reference from `can/util/library` to `can/util`.

changed reference from `can/util/library` to `can/util` to fix the
dependency. This does seem to work for both the steal and the amd
versions.
Fix for custom tags in IE8 using stache

This fixes a bug where custom tags used in IE8 would result in the tags
not being part of the document's namespace and therefore would be
rendered like: <:my-tag></:my-tag>.  This would also break for
non-custom tags like <header> and <footer> because stache uses
`cloneNode` which is not fixed by html5shiv.

The fix is a custom `cloneNode` for browsers with this issue that
recursively creates elements as a replacement for the browser's
cloneNode. Fixes #985
Changing filename to lowercase and adding value="" to default options