Opened 10 years ago
Closed 6 years ago
#11691 closed enhancement (wontfix)
ContentPane: defer parsing/DOM instantiation until first show
Reported by: | bill | Owned by: | bill |
---|---|---|---|
Priority: | low | Milestone: | 2.0 |
Component: | Dijit | Version: | 1.5 |
Keywords: | Cc: | ||
Blocked By: | Blocking: |
Description
ContentPane doesn't load it's href until it's first shown (ex: that TabContainer tab is selected, or that TitlePane is opened).
Thanks to [22835], we can do the same thing when the ContentPane's initial content is specified directly via:
new dijit.layout.ContentPane({content: ...})
or
<div dojoType=dijit.layout.ContentPane>...</div>
This will be a slight performance boost.
Marking for 2.0 since it's a slight break in backwards compatibility (in case any developers are depending on those widgets being created on page load). They can still achieve that though via the preload=true flag.
Change History (2)
comment:1 Changed 8 years ago by
Priority: | high → low |
---|
comment:2 Changed 6 years ago by
Resolution: | → wontfix |
---|---|
Status: | new → closed |
Note: See
TracTickets for help on using
tickets.
Closing this as wontfix. In https://github.com/ibm-js/delite (and other polyfill libraries) we shim how Custom Elements natively work, where custom elements are instantiated automatically. Therefore it's not possible to "defer parsing".