incubator-callback-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Patrick Mueller (Created) (JIRA)" <>
Subject [jira] [Created] (CB-89) Support Firefox Mobile (Fennec) as debug target
Date Tue, 29 Nov 2011 18:09:40 GMT
Support Firefox Mobile (Fennec) as debug target

                 Key: CB-89
             Project: Apache Callback
          Issue Type: New Feature
          Components: weinre
            Reporter: Patrick Mueller
            Assignee: Patrick Mueller


*brion (Brion Vibber) opened this issue July 28, 2011*

Since the debugging shim in the web page runs in native JavaScript, it ought to be possible
in theory to use weinre with non-WebKit debugging targets as long as the JS can get the info
it needs. This could be quite handy for testing a mobile web app on several browsers including
Firefox for Android & Meego.

I did a quick test with Firefox 5.0.1 on the desktop to see how much works with weinre (my
copy of Android firefox is currently not working for unrelated reasons, but it's built from
the same codebase as desktop firefox and should behave about the same).

inspector... sorta works:
* HTML tree looks ok
* ... but no highlight of selected item
* ... no computed style/styles/metrics info
* ... properties are mislabeled (but this seems to be same problem using Chrome and in the
OSCON demo, so may be a regression in the inspector or weinre itself)
* ... no event listeners info (but also doesn't work in Chrome 12)

basic console works:
* evaluate alert('hey')
* evaluate 25 + 32, get 57
* evaluate $('p').css('color', 'red') on a jQuery-using page; it works, and shows a list of
HTMLParagraphElements as expected

* 'databases' is blank (ff has no websql support so that's probably fine!)
* 'local storage' and 'session storage' on the localhost does show entries... but they're
the setItem, clear, and removeItem methods. :)

* appears to work similarly to target in Chrome

Even with the limited inspector, I would probably find this useful already. :D

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:!default.jspa
For more information on JIRA, see:


View raw message