dojo.moduleUrl bug

[ben hockey]

dojo.moduleUrl is giving the wrong output for custom module paths

dojo.registerModulePath('foo', '../../foo');
console.log(dojo.moduleUrl('foo').toString());
console.log(dojo.moduleUrl('foo', 'bar').toString());

try the above using the firebug console at ​http://archive.dojotoolkit.org/nightly/dojotoolkit/dijit/tests/form/test_Button.html and the output will be

../../../dojo/../../foo/
../../../../foo/bar

the issue is unrelated to the test page - i just picked an arbitrary public page which has dojo enabled.

[ben hockey]

FYI - the expected output can be seen in dojo 1.1.1 - try ​http://download.dojotoolkit.org/release-1.1.1/dojo-release-1.1.1/dojo/tests/test_fx.html

[bill]

(sadly) punting seemingly abandoned ticket and meta tickets to future

[bill]

I tried

dojo.registerModulePath('foo', '../../foo');
console.log(dojo.moduleUrl('foo').toString());

against ​http://download.dojotoolkit.org/release-1.4.0/dojo-release-1.4.0/dojo/tests/test_fx.html and it's printing out ../../../foo/, same as for 1.1 and 1.7.

Seems to be working for me, even against the version you specified. Is there something I missed?

[ben hockey]

i can't seem to reproduce anything now and amd deprecates most of this.