Differences between 1.6 and 1.7

Authors:Yoshiroh Kamiyama

Differences from 1.6


  • Added support for jsId.
  • Added dojo.parser = dojox.mobile.parser; so that other modules or user applications can directly call dojo.parser even when dojox.mobile.parser is used.
  • Updated signature of parse() and instantiate() to align with dojo.parser’s ones.
  • The 2nd argument of instantiate(), ‘defaultParams’, will no longer be mixed-in to widget parameters. It could break the widget, and the behavior is different from dojo.parser.
  • Respect the noStart flag. If it is specified, startup() of the instantiated widget will not be called.
  • Added support for the html5-style attributes, data-dojo-*.


  • Separated from _base.js and created dojox/mobile/Button.js. This means your application needs to add dojo.require(“dojox.mobile.Button”) if you use the button.
  • btnClass has been changed to class. You need to specify a button class using the class attribute as follows.
  • <button data-dojo-type=”dojox.mobile.Button” class=”mblBlueButton”>OK</button>
  • The default button class no longer exists. You always need to explicitly specify a button class such as “mblBlueButton”.


  • FlippableView has been renamed to “dojox.mobile.SwapView”.


  • You no longer need to add “mblDomButton” to the ToolBarButton class. It will be automatically added programmatically.


selected=”true” is no longer necessary if you just want to show the first view at startup. If you want to show a view other than the first one, adding selected=”true” is still effective.

New Features in 1.7


This module detects mobile devices from User-Agent string, and automatically loads an appropriate theme. The default is the iPhone theme. You can also explicitly specify which device theme to load via query string in the URL. Below is examples.

  • theme=Android
  • theme=BlackBerry
  • theme=iPad
  • theme=iPhone (default)

Ex. test_transition-animations.html?theme=Android

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