History log of /yui3/src/widget-parent/tests/parent-child.html
Revision Date Author Comments Expand
dffbe2d4e60ed4db1cecdea6cec2041eed9ff555 17-Mar-2012 Satyen Desai <sdesai@yahoo-inc.com>

* More filling out of parent/child unit tests. * Found a bug in the process. Removing a focused child does not reset the parent's activeDescendant state (it was using child.set("focused", false), which is readOnly. Changed to child.blur(). Fixes #2531907

ca4cb3af5af57ff62359482f6b9106dde7091717 16-Mar-2012 Satyen Desai <sdesai@yahoo-inc.com>

Filled out line level coverage for Parent/Child selection

1df84ffb9aca4272e816ec9205c44b42161d9252 15-Sep-2011 Satyen Desai <sdesai@yahoo-inc.com>

Fixed issue where previously rendered children, added to an empty parent, would not get rendered into the parent's child container node. Based on the pull request from andreas-karlsson, with the root fix *and* unit test (nicely done): https://github.com/yui/yui3/pull/25 Fixes #2531093

df315088426ba61b1911bca0c888843588e552e9 13-Sep-2011 Satyen Desai <sdesai@yahoo-inc.com>

Added additional check in _uiAddChild, to make sure prev/next sibling is rendered before trying to insert content relative to it. NOTE: This fix is not really required for the out-of-the-box parent/child implementation, but came up because a user had a custom impl. which made child.render() async [probably a valid usecase for parent/child]. See Fixes #2529863

153a5c4700cc6ab14ac1898ab461a13f738f4d1e 09-Sep-2011 Satyen Desai <sdesai@yahoo-inc.com>

Added unit test for removeChildOnDestroy implementation. NOTE: No code was changed in 3.4.1 for removeChildOnDestroy. Just came across the impl while fixing #2529785, and added the unit test

c5d69e6f30e09e2833161efb5393ecc8a8c9d8d6 09-Sep-2011 Satyen Desai <sdesai@yahoo-inc.com>

Use extension destructor support, rather than AOP'ing destructor, which won't work. Fixes #2529785

1bb9ba7f0e700971d0c04fca23820699348cfd49 07-Sep-2011 Satyen Desai <sdesai@yahoo-inc.com>

Prepped tests for coverage reporting

37c410fc73ed5acc3161813869a31de525b5aa2e 15-Jun-2011 Satyen Desai <sdesai@yahoo-inc.com>

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

5d6602ccab9b5300134be9f9c206a815d1df3ecc 30-Nov-2010 Satyen Desai <sdesai@yahoo-inc.com>

Added parentchild tests to smoketests

516282bd16544bd0fa68565203a4fa8ef51036c7 22-Oct-2010 Satyen Desai <sdesai@yahoo-inc.com>

Fixed WidgetParent remove, to remove child from DOM also. Added tests cases. Fixes #2528911

78b2f85243d415328c137882ec8f12fd5d3ae5c7 22-Oct-2010 Satyen Desai <sdesai@yahoo-inc.com>

Fixed WidgetParent remove, to remove child from DOM also. Added tests cases. Fixes #2528911

9aa013e47e1dda95efef1ef853b8df4a7d850a9d 22-Oct-2010 Satyen Desai <sdesai@yahoo-inc.com>

Added childType test

c2591f93148f34add0265b627e2198f1cea598f6 06-Oct-2010 Adam Moore <adamoore@yahoo-inc.com>

build tweaks, optimizations

ae0acbc28a5e36314d44af9ffa26ca678e545756 05-Oct-2010 Adam Moore <adamoore@yahoo-inc.com>

build tweaks, optimizations

8210c45660fdfb72dd288f258040dd11b6ba71b2 12-Mar-2010 Satyen Desai <sdesai@yahoo-inc.com>

Changed focusedChild (back) to activeDescendant. Turns activeElement is supported by the A-Grade, and is in the HTML5 spec. Also changing it to descendant, rather than child seemed to make sense as the low-level state, since only one widget actually has real focus. activeChild can be calculated from activeDescendant. See #2528688

761b73849453c76dd2e3e60aee5c1e4368017717 11-Mar-2010 Satyen Desai <sdesai@yahoo-inc.com>

Renamed activeItem to focusedChild as per comments in bug report. Fixes #2528688. Also cleaned up some temp sandbox files.

d0a16c48f3477794c63f4ff3242dc20db6a49295 22-Feb-2010 Satyen Desai <sdesai@yahoo-inc.com>

tests cleanup (yui- to yui3-)

cf8ec1f7a476d02f1a43bda999dc075e8546ee27 11-Feb-2010 Todd Kloots <kloots@yahoo-inc.com>

Initial checkin of test cases for the Widget Parent and Widget Child extensions