Remove dojo.widget._cssFiles in favor of using feature built into insertCssFile

[sjmiles@…]

Seems like the dojo.widget._cssFiles registry and it's usage here

line 42, DomWidget?.js: if((cpath)&&(!dojo.widget._cssFiles[cpath])){

dojo.xml.htmlUtil.insertCssFile(cpath); dojo.widget._cssFiles[cpath] = true;

}

is something that would be good in the API somewhere.

Fwiw, I'm already using the array in my code.

[sjmiles@…]

As I should have included, I use it like so:

turbo.loadCss = function(inPath) {

if ((inPath)&&(!dojo.widget._cssFiles[inPath])) {

dojo.xml.htmlUtil.insertCssFile(inPath); dojo.webui._cssFiles[inPath] = true;

}

}

[schontz@…]

For what it's work, insertCssFile already allows you to avoid duplicates. The widget code should be updated to take advantage of this.

dojo.xml.htmlUtil.insertCssFile(cssFile, null, true); // checks for dups

[anonymous]

Fwiw, I tried using the 'checkDuplicates' feature of insertCssFile and I ended up with multiple copies of some of my CSS files and no copies of others.

The registry solution seems much simpler as less prone to browser-issues, but maybe I'm channeling Cassandra.

[sjmiles@…]

checkDuplicates is failing because of problem comparing URI objects with ==. See #97:http://dojotoolkit.org/trac/ticket/97.

[bill]

_cssFiles is gone altogether in dijit.