discrepancy debugging touch apps in firefox vs chrome?

[ktcpf]

I know that webkit browsers are the way to go when debugging touch apps.

The Kitchen sink tells me that I should only run it in a webkit browser.

Generally I use Chrome for my debugging, but I've found that the developer tools don't give me a whole lot of information out of the box. When I add any Ext object to my watches it gets labeled "Ext.apply.create.Class" and digging through that massive stack of properties on every ext object is not intuitive to me. I'm having trouble even finding out what types my objects are - Ext.getDisplayName(object) - but I have to re-do it every time.

http://www.illuminations-for-developers.com/
There's a firebug plugin called "Illumination" that I've been using. But this is a plugin that only runs in firebug (in firefox).

for instance :

this line of code
myStore = Ext.create ("cpftest.store.QuickTemplates");


when I look in firebug I get
object { ... }
and the first line when I expand the object in the debugger is
"$classname : cpftest.store.QuickTemplates"

when I look at it in chrome's debugger I get
Ext.apply.create.Class

and when I expand the object to try to dig out the class name I have no idea where to look.

Is there some trick to debugging touch in chrome that I'm missing?

[mitchellsimoens]

Sencha Touch does not support firefox. Expand the class you console logged and you can see what it is.

[jay@moduscreate.com]

Touch is Webkit and IE10 only.

[mitchellsimoens]

IE10 only.

For ST 2.2 (just a note for any readers)