Changes between Initial Version and Version 1 of Ticket #9897


Ignore:
Timestamp:
Sep 16, 2009, 6:17:28 AM (10 years ago)
Author:
bill
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #9897 – Description

    initial v1  
    77}}}
    88
    9   2. after ther parse, there's a dojo.require("dijit.layout.!BorderContainer"), or !TabContainer, etc, some class that adds new parameters to _Widget
     9  2. after the parse, there's a dojo.require("dijit.layout.!BorderContainer"), or !TabContainer, etc, some class that adds new parameters to _Widget:
     10{{{
     11dojo.extend(dijit._Widget, {
     12        // region: [const] String
     13        //              "top", "bottom", "leading", "trailing", "left", "right", "center".
     14        //              See the BorderContainer description for details on this parameter.
     15        region: '',
     16...
     17});
     18}}}
    1019
    11   3. parser is called again, to parse another !ContentPane that defines the new parameters like region, etc:
     20  3. parser is called again, to parse another !ContentPane (inside a !BorderContainer) that passes the new parameters like region:
    1221{{{
    1322<div dojoType=dijit.layout.ContentPane region=top>
    1423}}}
     24
     25The parser won't pick up the region parameter and thus the !BorderContainer won't layout correctly.
    1526
    1627I think this actually might be a common case for dojox.layout.!ContentPane, when the href-loaded content does dojo.require() calls.