Use a better onload/onreadystatechange fork Failing test in FF due to s.onload = ';' + (typeof s.onload === 'string') test. Expecting 'function' in all but IE, but FF 3.6 and 4 return 'string', so were getting the onreadystatechange fork, resulting in test failure. Changed to a carpet bomb approach. Assign both onload and onreadystatechange regardless of env and keep track of which worked. Not pretty, but it gets the job done. I then lost a couple hours tracking why the test was suddenly failing in IE 9, only to discover that I'd reduced the response delay to close to the configured timeout for the test send(), resulting in a race condition. I want my time back. And maybe a drink.

Split jsonp and jsonp-url test page into one each The test reporting automation used the Runner's complete event to log results. The jsonp tests monitor the state of the global proxy cache YUI.Env.JSONP. To keep the test env clean for the jsonp-url tests, a new YUI instance is created, but the two instances share the global space (which is ok), causing some tests to fail randomly when assertions about the global proxy cache get info from the other YUI instance. I avoided this by putting the jsonp-url tests in a callback to Runner's complete event to create the other YUI instance, and use() and execute the tests, but because the test reporting tools also listen to the complete event, this causes only one set of tests to be reported. Simple answer: use a separate file for each module.

Track requests and timeouts for every JSONPRequest The logic to prevent other callbacks from executing after a timeout was limited to connections with allowCache=true. Fixes #2530352

Normalize YUI config for tests. filter from url. Use the query string filter={raw|debug} to override min default filter applied to YUI config.

Add jsonp-tests to YUI instance testing jsonp-url Since jsonp is a requirement of jsonp-url.

Properly segment submodule tests. Add some more. Test page now includes a separate YUI() for each submodule test suite.

Move tests from sandbox to src/X/tests/src Adapt to test structure enforced by new builder target 'tests'. Still more cleanup to do. But hopefully I didn't miss anything. C'mon CI!

Update tests to reflect callback={callback} for base I broke YQL when removing jsonp-url from the 'jsonp' module (formerly a rollup) because it expected YQL.BASE_URL to include "callback={callback}", but YQL was using the feature added by -url whereby that string would be auto-added if not found in the url. For 3.2, the YQL Loader meta was updated to require jsonp-url, but for 3.3 either YQL should be updated or jsonp (base) should absorb the auto-add feature. The tests changed here were also working from the auto-add assumption, but no errors showed because it is also testing jsonp-url.

Test file updates for jsonp module structure change

Use path parser from dataschema-json. Fix tests. IE throws when trying to delete window.property, so set to undefined in the tests that exercise the url parsing for global callbacks. The js-syntax parsing regex algo was faulty, as discovered by the false positive tests that should have failed due to a typo in the tests. I wrote a more comprehensive one for dataschema-json long ago, so copy/pasted that one until we can extract to a common util.

IE 6 doesn't like width: 'inherit' declaration in Console

Simplify url callback parsing, Extract to submod. Split into jsonp-base and jsonp-url. Base does simple, single level name resolution for callback-in-url parsing (callback=foo, or callback=Y.foo). Nested parsing moved to jsonp-url (callback=foo.bar["baz"]).