| Commit message (Collapse) | Author | Age |
... | |
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
| |
e.g. IE11
Instead iterate over string contents and manually build hash.
I have *not* tested this for performance.
An alternative option is to use Array.prototype.join.call
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
might not be available in older environments
|
| |
|
| |
|
| |
|
|
|
|
| |
cached manually
|
| |
|
|
|
|
| |
bytes
|
| |
|
|
|
|
| |
Doesn't work in web workers
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
reponse type where possible
|
| |
|
| |
|
|\ |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
| |
| |
| | |
Using .indexOf seems to benchmark faster than iterating
|
| | |
|
| | |
|
|/ |
|
| |
|
|
|
|
| |
This should avoid errors thrown by to_jsstring
|