-
jeresig authored
Try to use the native JSON parser in all cases and fallback to the old technique otherwise. This allows us to also handle cases where the JSON parser is unable to parse JSON-like strings correctly (e.g. {foo:bar}) which is something that worked before but would stop working with the switch to the new parser.ff3645ee
| Name |
Last commit
|
Last update |
|---|---|---|
| .. | ||
| ajax.js | ||
| attributes.js | ||
| core.js | ||
| css.js | ||
| data.js | ||
| dimensions.js | ||
| effects.js | ||
| event.js | ||
| intro.js | ||
| manipulation.js | ||
| offset.js | ||
| outro.js | ||
| queue.js | ||
| sizzle-jquery.js | ||
| support.js | ||
| traversing.js |