The Following 3 Users Say Thank You to juiceme For This Useful Post: | ||
![]() |
2016-03-04
, 14:56
|
Posts: 602 |
Thanked: 735 times |
Joined on Mar 2011
@ Nantes, France
|
#2
|
The Following User Says Thank You to romu For This Useful Post: | ||
![]() |
2016-03-04
, 16:29
|
Community Council |
Posts: 4,920 |
Thanked: 12,867 times |
Joined on May 2012
@ Southerrn Finland
|
#3
|
![]() |
2016-03-04
, 17:18
|
Community Council |
Posts: 4,920 |
Thanked: 12,867 times |
Joined on May 2012
@ Southerrn Finland
|
#5
|
The Following User Says Thank You to juiceme For This Useful Post: | ||
![]() |
2016-03-04
, 17:49
|
|
Posts: 394 |
Thanked: 1,341 times |
Joined on Dec 2009
|
#6
|
The Following User Says Thank You to velox For This Useful Post: | ||
![]() |
2016-03-04
, 17:49
|
Community Council |
Posts: 4,920 |
Thanked: 12,867 times |
Joined on May 2012
@ Southerrn Finland
|
#7
|
![]() |
2016-03-04
, 17:54
|
Community Council |
Posts: 4,920 |
Thanked: 12,867 times |
Joined on May 2012
@ Southerrn Finland
|
#8
|
Back in the day when android/ios didn't support remote debugging there was this project called weinre – sadly most of the documentation is now 404. But there's some code mirrored at the apache cordova github. Perhaps you can get it running. It emulates the dev tools on your phone and displays it at a remote chrome instance.
Also, something like jsconsole might help you (I have not tested it!).
Current known support
Remote debugging has been developed to work on all platforms, even if the technology isn't supported. However, jsconsole remote debugging has specifically tested and working on the follow mobile devices (feel free to add to this list):
- iOS 4.2.x - iPad, iPhone 4
- Andriod 2.2.2 - Nexus One
- webOS - Palm Pre
![]() |
2016-03-04
, 18:01
|
|
Posts: 6,436 |
Thanked: 12,701 times |
Joined on Nov 2011
@ Ängelholm, Sweden
|
#9
|
The Following User Says Thank You to coderus For This Useful Post: | ||
![]() |
2016-03-04
, 18:07
|
|
Posts: 394 |
Thanked: 1,341 times |
Joined on Dec 2009
|
#10
|
i think you need to write some extension sending you jsconsole logs, as it can be not bridged from gecko to qtmozembed/embedlite components
The Following User Says Thank You to velox For This Useful Post: | ||
There's no developer tools window AFAIK.
When sailfish-browser is started from the shell it does display quite useful debug messages but no output from javascript, so where do my console.log() prints go to?
The reason why I am curious about it is that I have an application that works correctly in Firefox and Chrome but fails on my Jolla device.