Changes between Initial Version and Version 1 of Ticket #10807


Ignore:
Timestamp:
Mar 2, 2010, 3:20:31 PM (10 years ago)
Author:
bill
Comment:

Thanks for the test case.

One thing I noticed off the bat is that you are calling startup() on widgets that haven't been attached to the document yet. That's illegal. Also, your test doesn't include dojo.js.

Fixing those two things though, I do see the problem, I'll fix it somehow. I'll attach the updated test case

Legend:

Unmodified
Added
Removed
Modified

  • Ticket #10807

    • Property Owner changed from anonymous to bill
    • Property Component changed from General to Dijit
    • Property Milestone changed from tbd to 1.5

  • Ticket #10807 – Description

    initial v1  
    1 Since [http://trac.dojotoolkit.org/changeset/21203 revision 21203], if you pass a TabContainer in as the content of a TooltipDialog and then create and startup() a DropDownButton with the TooltipDialog as dropDown, tabs added after the button startup() is called do not appear.  They are in the HTML, but have a position: absolute style which seems to stop them being displayed.
     1Since [21203], if you pass a !TabContainer in as the content of a !TooltipDialog and then create and startup() a !DropDownButton with the !TooltipDialog as dropDown, tabs added after the button startup() is called do not appear.  They are in the HTML, but have a position: absolute style which seems to stop them being displayed.
    22
    3 If, after the DropDownButton is created and started, the content of the TooltipDialog is set to the TabContainer (instead of at creation), this problem does not appear.
     3If, after the !DropDownButton is created and started, the content of the !TooltipDialog is set to the !TabContainer (instead of at creation), this problem does not appear.
    44
    55I will attempt to create a simple test case, as this is not the clearest explanation.  This is with version 1.4.1, which version does not seem to have been created.