How to debug firefox noshow without stacktrace?

[Jonathan Gerber]

I have been happily coding away, testing my work in the latest version of chrome. However, when firing up my app on firefox, I get nothing. Not even a javascript complaint. The app makes use of an auto-binding template to wrap everything and the only html which shows up in the body is the template and nothing inside of it.  So... how does one go about debugging something like this? Pointers would be appreciated. In the past, when encountering errors, I have always had a stacktrace to start with. Pointers would be much appreciated.

[Cayter Goh]

I think it's always better to paste your codes somewhere else so that others can help troubleshooting. :D

[Rob Dodson]

Maybe start by removing stuff until your app renders again and add it back piecemeal. Also, sharing your code as Cayter pointed out will help :)

On Sun, Feb 8, 2015 at 2:05 AM, Cayter Goh <cay...@appist.io> wrote:

I think it's always better to paste your codes somewhere else so that others can help troubleshooting. :D

Follow Polymer on Google+: plus.google.com/107187849809354688692
---
You received this message because you are subscribed to the Google Groups "Polymer" group.
To unsubscribe from this group and stop receiving emails from it, send an email to polymer-dev...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/polymer-dev/6286012e-9817-4007-abda-b05312d76898%40googlegroups.com.

For more options, visit https://groups.google.com/d/optout.