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.

Cleanup for focus listener optimization. Reverting mousedown focus handling to be instance based. Fixes #2529502.

More changes to the way we store the Widget.getByNode cache. It's an implementation detail but we're now using boundingBox id, as opposed to yuid (which is really an internal Node detail and seems fragile - say we start clearing Node cache periodically). Only reason it may break is if folks are flipping boundingBox node ids after they've been provided to widget, which seems unlikey/unwise, but that's why I wanted to get it into PR1.

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

Refactored some Widget stamping and destruction code to allow for pure string based renderering. Avoids a potential WidgetHTMLRenderer implementation we're looking at for TreeViewNode from having to override it. Unit tested on FF/Chrome/IE6/IE9

Clean up 3.4.1 HISTORY files.

Updated HISTORY.md files to have unified title headings. Some HISTORY.md files had incorrect title headings, so these changes fix the incorrect ones and unify their format: "[Component] Change History".

Try to fix line breaks in HISTORY.md

add more detailed comment about detroy() change from checkin text

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

Widget README -> README.md + HISTORY.md