Added yeti focus exceptions for yeti && gecko, and for event-touch tests

Filling out line level coverage for base, base-core, widget

un-ignored testWidgetOnFocus. Passes on IE, FF, Chrome, Safari with fix for See #2531734. Fixes #2531335

Added widgetOnFocus test. Currently ignored until See #2531734 See #2531335 are fixed

Widget's constructor now does a config = config || {} before chaining to Base's constructor, so that HTML_PARSER works when constructing a widget without providing a configuration object. This could happen when srcNode is defined statically. Rare, but probable use case for JS Widgets which are tightly bound to server side HTML impls. Fixes #2531501 Ran all unit.xml units tests through yeti, since this is fairly low level.

2nd pass at focus optimization. Cleaned up active handling (still some potential gaps)

Changed test order for events to focus and then hide, instead of hide then focus to provide predictable results across browsers

Added patch for homogenous bubble issue, until we roll root fix into Event/EventTarget. Fixes #2529582. See https://gist.github.com/1356718 for potential Event solutions

tabIndex is now sync'd to DOM post render. No idea why we weren't doing this before. Fixes #2531105

Last one, I promise (for now)

Wrap up widget unit tests

More Widget Tests

Uncommented autorun in widget tests

More Widget Tests. More To Come.

Added widget core unit tests

More widget tests

Added widget core unit tests

Prepped tests for coverage reporting

Added support for destroy(true) to Widget, which will remove and destroy all child nodes (not just the boundingBox and contentBox) contained within the Widget's boundingBox in order to help control Node cache size over long-running applications. destroy() will maintain it's current behavior due to the potentially high run-time cost of destroying all child nodes. Widget developers still need to continue with the best practice of destroying explicit node references they create, in their destructors to support the destroy() case. If you destroy Widgets in your application or are a custom widget developer, your help in testing this change before release is much appreciated. Fixes #2530444

Fixed regression in ParentChild caused by Widget nested UIEvent fixes. Fixes #2530400

Added widget Multiple Y instance UI_EVENTS test. See #2529724

Fixed UI_EVENTS invoking nested Widget listeners more that once. Added UIEvents test cases (that Ryan Grove is a bad influence). Fixes #2529723

Added workaround for widget destructor. May revert once/if calling Node.remove multiple times on the same Node instance, is resolved. Fixes #2529860, See #2529851. Also pulled the node removal out into a separate method, so behavior can be overridden in cases where the srcNode needs to be maintained.

Pulled in modified tests (names, no console) from 3.1.0+ branch

Updated widget test case

Added test case for Widget cloning

Added unit tests for destroy

Fixed destroy before render. Fixes #2528678

tests cleanup (yui- to yui3-)

Adding widget.getSkinName() to return "sam" when widget DOM inside <div class="yui3-skin-sam">. Added test suite Test.Case accordingly.