IconItem moveTo overlays 2nd view on top of 1st view

[jonferraiolo]

I verified this problem with both dojo 1.8.3 and dojo 1.9.0rc1.

I have attached an HTML file (and associated screenshot) for a case where if you put a 'moveTo' property on an IconItem?, then clicking on the IconItem (using Mac/Chrome) will cause the second View will overlay the contents of the first View.

(The file was originally created in Maqetta, but then the Maqetta-specific markup was cleansed from the source code, and the effect happens without Maqetta being involved.)

[jonferraiolo]

HTML source code

[jonferraiolo]

Screen snapshot showing currupted result

[Adrian Vasiliu]

The behavior that you observe is due to the fact that your code specifies an unsupported value for the transition type:

<li label="Item 1" data-dojo-type="dojox/mobile/IconItem" 
  transition="below" ...>

while as documented the supported values are: "slide", "fade", "flip", "cover", "coverv", "dissolve", "reveal", "revealv", "scaleIn", "scaleOut", "slidev", "swirl", "zoomIn", "zoomOut", "cube", "swap", and "none".

Using for instance "slidev" instead of "below" fixes the problem in the browsers where I reproduced it with your code as-is. (Other browsers seem to tolerate it better.)

I tend to think it would be nice to provide error feedback in such case, however AFAIK this wouldn't be consistent with the current general Dojo policy (may change for 2.0).

For the time being, I'm closing the ticket, but of course feel free to ask to reopen if appropriate for some reason.

---

Finally, a few side-remarks about things that I've noticed in the sample code:

1. It is not recommended to load deviceTheme using the AMD loader (for details and replacement solutions: livedocs.dojotoolkit.org/dojox/mobile/deviceTheme)
2. As long as you use dojox/mobile widgets, I see no reason to set the claro class on body.
3. Instead, it is generally recommended to set style="visibility:hidden;" on body, such that the user sees the app only once it is nicely styled.
4. It would be better to set the widget properties in markup using data-dojo-props rather than as attributes.

These points don't matter for this issue but may cause troubles in other cases.