#5697 closed defect (fixed)
Lazy Loading the AccordionContainer doesn't work
| Reported by: | ptwobrussell | Owned by: | bill |
|---|---|---|---|
| Priority: | high | Milestone: | 1.1 |
| Component: | Dijit | Version: | 1.0 |
| Keywords: | Cc: | dante | |
| Blocked By: | Blocking: |
Description
As of today's nightly test, the lazy load demonstration for the AccordionContainer? doesn't work; You can watch Firebug and verify that the href child content gets loaded on page load, not when you select it. dante seems to think that it used to work and that this is not related to "de-supporting" AccordionPane?'s ability to house complex layout dijits, so I'm filing this ticket to track the status.
Change History (4)
comment:1 Changed 11 years ago by
| Owner: | set to bill |
|---|
comment:2 Changed 11 years ago by
| Resolution: | → fixed |
|---|---|
| Status: | new → closed |
(In [12691]) Fixes #5697: Lazy Loading the AccordionContainer? doesn't work
comment:3 Changed 11 years ago by
(In [12692]) Refs #5697: previous checkin was incorrect; for TooltipDialog? etc. this.containerNode exists, but visibility is still set on this.domNode. (OTOH for TitlePane? and AccordionPane?, visibility of the section w/the href is controlled on this.containerNode)
comment:4 Changed 11 years ago by
(In [12822]) Don't check this.selected to see if a ContentPane? is shown or not. If StackContainer/TabContainer? is included on the page then every ContentPane? has a "selected" attribute, even if it isn't a child of a StackContainer?. Fixes #6048, refs #5697.
Hmm, this is probably my fault from the work for #5669 and #5670.