Thread: JavaScript debugging in mobile browser and WAF
View Single Post
Old 03-05-2019, 03:02 PM   #2
knc1
Going Viral
knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.
 
knc1's Avatar
 
Posts: 17,212
Karma: 18210809
Join Date: Feb 2012
Location: Central Texas
Device: No K1, PW2, KV, KOA
Quote:
Originally Posted by jnjitkoff View Post
Hi all!

Does anyone have any pointers for the best way to get javascript console output in the Kindle experimental browser? I'm struggling to identify which apis are present in that version of WebKit (things like promises and fetch didn't exist yet).

I'd love to be able to catch those errors in a more elegant way than document.write on window.onerror.

Any help would be much appreciated!
The experimental browser may vary by both firmware version and Kindle model.
So start out with telling us the model other than just "Kindle":
https://wiki.mobileread.com/wiki/Kindle_Serial_Numbers
And then tell us what firmware version it is running;
you can find that on the "Device Info" panel under the "Settings" menu.
knc1 is offline   Reply With Quote