Hacker News new | past | comments | ask | show | jobs | submit login

Five years ago or so, you could debug extensions with Chromebug, based on Firebug. It is what we used to debug Firebug itself. But when Mozilla decided to go and split out its own DevTools about three years ago, the writing was on the wall, and the lead developer John left. Unfortunately, he was the only one that really understood Chromebug, and Mozilla kept changing things that broke it with each new version of Firefox.

If you think debugging your extension is hard, imagine debugging Firebug. We built our own tracing/logging extension a long time ago to help, and I think it predates Chromebug. But it is not the same.

Fact is, Mozilla extensions are going to have some issues when e10s ships in final form. It can give then the opportunity to redo things. I'm not a fan of JetPack, btw, as I think python is a requirement. And not the version I have on my machine. Talk about a non-starter.

At least the built in tools are finally getting to a useable state. They are made for e10s. They have some nice features. I haven't noticed them breaking sites that you debug by being them being turned on (my fault for waiting so long to file a bug). They have some great UI choices (yet some bad ones). Overall, they are shaping up.

BTW, the debugging of extensions only works for some extensions. Sadly not mine. :/




Steve, the browser debugger should work with all extensions... what isn't working for you?




Join us for AI Startup School this June 16-17 in San Francisco!

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: