Frequently Asked Questions

Authors:Yoshiroh Kamiyama is an extremely small subset of dojo.parser. It has no extended features, so there is no reason you have to use instead of dojo.parser. However, if’s capability is enough for your application, use of it could reduce the code size.

What is the difference between and dojo.parser?

Some of the advanced features of dojo.parser, such as <script type=”dojo/method”> and <script type=”dojo/connect”>, are missing. Basic features are compatible with dojo.parser.

How is the size of compared to dojo.parser?

As of dojo-1.7 beta3, the size of is 1KB (built & gzipped), while dojo.parser (plus its dependent modules that are not required by the base) is 10KB.

Do I have to use for applications?

No, you don’t have to. is a subset of dojo.parser. Usage and how it works are basically the same. If your application unfortunately does not work with, you can replace it with dojo.parser.

Can I use for desktop dojo applications?

Yes. Use of is not limited to mobile. It has enough capability to bootstrap simple dojo applications. This may sound strange, but has no dependency on (And has no dependency on either.) So you can pick up only and use it for your desktop applications. Actually, this parser was originally developed for very lightweight desktop dojo applications a few years before was born.

However, cannot be used for applications that contain ContentPane subclasses with nested widgets, since those nested widgets will try to be instantiated twice. For example:

<div data-dojo-type="dijit.Dialog">
    <button data-dojo-type="dijit.form.Button">OK</button>

Also note that loading some desktop widgets may implicitly load the dojo.parser.

Android Issues

I can’t seem to run Dojo Mobile pages on Android devices when using libraries like PhoneGap, what am I doing wrong?

There is a known bug in the Android WebKit browser implementation that does not allow files starting with an underscore ‘_’ character to be loaded from local file system (for example when using Dojo Mobile in conjunction with PhoneGap to create a native app). The way around this problem is to create a built version of your files (you’ll want to do this anyway for performance).

mblAlwaysHideAddressBar does not work on my Android device. What’s going on?

mblAlwaysHideAddressBar does not work on some Android devices when overflow:hidden style is applied to html and body tags. This overflow:hidden style is used in some test cases including test_ScrollableMixin-custom.html for desktop browsers not to show scroll bar, but you can remove it for mobile browsers so that you can hide address bar.


Why does <body> in many of tests html files have style=”visibility:hidden;”?

It is to prevent raw HTML rendering result from being shown before dojo’s rendering finishes. The visibility will be restored by the initialization code in

Error in the documentation? Can’t find what you are looking for? Let us know!