After much deliberation with the layout tab in firebug – I found that this div (with no explicit height set) was not expanding  to accommodate the children inside. Further investigation pointed to the fact that the child nodes in question were actually floated & therefore they were outgrowing the parent.

http://www.tangible.ca/article_resources/expanding_divs_around_floats/ had described this exact problem succintly & provided an simple solution.

Consider the code snippet

<div id=”parent”>

<div id=”floatedchild1″></div>

………………..

<div id=”floatedchildn”></div>

</div><!– parent node ends –>

Before the parent div is closed – we would need to introduce

<div style=”clear:both”></div>

that would solve this seemingly complex issue.

Happy Coding & learning!!!!

1. console.exception(error object) – to print stack trace

2. console.time(“some message”);…..piece of code to measure time…..console.timeEnd(“some message”); – to print the time taken of the code in between

3. console.group & console.groupEnd – print messages in Hierarchy/Groups

More such functions in Console API Documentation of Firebug

2. http://www.linuxjournal.com/magazine/dojos-industrial-strength-grid-widget

3. http://dojotdg.zaffra.com/category/articles/

4. docs.dojocampus.org

Dojo dead end - not able to see the code of internally loaded modules

Other alternative is to use the djconfig.debugAtAllCosts by making the following change.

Enabling debugAtAllCosts

Thus we could use this flag to make sure dojo uses dynamically inserted script tags to load the various modules.

With any facility, comes its own caveats to be beware of – debugAtAllCosts is no exception.

Kindly refer to the How DebugAtAllCosts Works for a detailed explanation on reasons related due to debugAtAllCosts can fail.

More into this my next post

items=[];//define a array
length=items.length;//throws error since the term length is treated special in IE
for(item in items){
//again the term item is treated in a special way in IE – would throw the same error.
}

Either make sure these are local variables by prefixing them with var.

items=[];//define a array
var length=items.length;//throws error since the term length is treated special in IE
for(var item in items){
//again the term item is treated in a special – would throw the same error.
}
otherwise rename the variables
items=[];//define a array
mylength=items.length;//throws error since the term length is treated special in IE
for(myitem in items){
//again the term item is treated in a special – would throw the same error.
}

After a lot of digging, I found that any variable declared without the var keyword is considered to global in Javascript. Specifically in IE – They get attached to a global collection called document.all.

So helper methods associated with document.all such as

1. item
2. namedItem
3. tags
4. urns

and the property “length” are all considered reserved with respect to global variables in IE.

Also refrain from using these words as IDs for any HTML element.

dojo.data.ItemFileReadStore: The json data as specified by: [/serverURL/that/returns/json/data] is malformed. Items within the list have identifier: [displayLabel]. Value collided: [<Actual value that collided >]

2. Hot flat and Crowded By Thomas Friedman

3. Happier than God By Neale Donald Walsch