Changes between Version 1 and Version 2 of Ticket #15174, comment 9


Ignore:
Timestamp:
Jun 20, 2012, 11:57:00 AM (9 years ago)
Author:
Adrian Vasiliu
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #15174, comment 9

    v1 v2  
    11Yes, an attempt to understand it is ongoing.
    2 For ContentPane, the story is the following: the test creates and fills the !ContentPane programmatically (for the failing case, with a "href"), then it used to check on the "loadHandler" event that the pane has a child. But this appears to be too early. I've tried to listen to "onLoad" instead of "loadHandler", but the behavior is the same. What did work is doing the checks in a setTimeout once getting the "loadHandler". So what needs to be clarified is the following: is the DOM supposed to be already filled when "loadHandler" (or "onLoad") are fired?
     2For !ContentPane, the story is the following: the test creates and fills the !ContentPane programmatically (for the failing case, with a "href"), then it used to check on the "loadHandler" event that the pane has a child. But this appears to be too early. I've tried to listen to "onLoad" instead of "loadHandler", but the behavior is the same. What did work is doing the checks in a setTimeout once getting the "loadHandler". So what needs to be clarified is the following: is the DOM supposed to be already filled when "loadHandler" (or "onLoad") are fired?
    33
    44Will also try to understand what's going on with the other tests that failed on my side (without the patch) while didn't on yours (in particular on Christophe's).