Firefox 18+ supports String#startsWith, String#endsWith
Optional position argument

Added optional position argument to `String#startsWith`, `String#endsWith`, as described in https://developer.mozilla.org/en-US/docs/JavaScript/Reference/Global_Objects/String/startsWith and https://developer.mozilla.org/en-US/docs/JavaScript/Reference/Global_Objects/String/endsWith.
Documented new arguments and examples.
Updated unit tests
Bugfix in toQueryParams (didn't decode '+' correctly)
Add documentation example for `Element#clone.`
Merge pull request #96 from victor-homyakov/patch-33

Use native `String#startsWith` and `String#endsWith` if present. Turn existing implementation into a true polyfill.
Merge branch 'master' of github.com:sstephenson/prototype
Add polyfill information to documentation for `String#startsWith` and `String#endsWith`.
Merge pull request #98 from kir/master

Ensure that '+' is correctly deserialized in `String#toQueryParams`.
Fix an issue with a capability check causing an error in IE 10.
Merge branch 'master' of github.com:sstephenson/prototype
Add space to separate existing filters from alpha filter

In IE <= 8 it was impossible to setOpacity on an element that already had an existing filter such as filter: FlipH; The filters need to be space seperated
Fixes scollTop property that is deprecated on body

Chrome 32 deprecates document.body.scrollTop, should use
document.documentElement.scrollTop instead. Polyfill describe here
https://developer.mozilla.org/en-US/docs/Web/API/Window.scrollY
Style and reduce redundant code
Merge pull request #110 from jwestbrook/cumulativeScrollOffset-fix

Fix use of `scrollTop` property in `Element.cumulativeScrollOffset`.
Fix failing string test in Chrome.
Update Sizzle to latest stable version.
Update include point for latest version of Sizzle.
Remove a failing test.

(Sizzle doesn't seem to support this anymore, which is fine with me because it's a ridiculous selector.)
Change failing tests.

One of these tests presumably tests comma handling — whether we do the right thing when the space is before the comma, or when there end up being duplicate commas — and this is not something we handled before, so if this is a newly-failing test it's because Sizzle used to handle this and now does not. That's fine with me.

The other one appears to be a disagreement over whether `:enabled` should match `input[type=hidden]`, and Sizzle apparently says it does, and I'm OK with that, too.