News for hackers. Stuff that matters.
Re:Ask HN: Webdevs, designers: what devtools should we (Mozi... by olivierbeaulieu on Tuesday March 05, 2013 @12:14PM (#5325734)
I work a lot on a Firefox extension, and honestly, the absence of dev tools for addons is really painful. Developping our extension for Chrome was super easy, since all their default devtools work in extension panels as well, but in Firefox it's been a nightmare, almost no tools. We are left off in a console.log madness trying to figure out what's causing bugs.

It would be soooooo awesome to have Firefox's default devtools working easily in extension panels!

Re:Ask HN: Webdevs, designers: what devtools should we (Mozi... by paisible on Tuesday March 05, 2013 @02:24PM (#5326705)
Agreed - we've built extensions for Chrome, Firefox, IE & Safari ; Firefox and IE are on the same level with regards to debugging, that is : not pleasant. It's a shame because browser extensions have great potential : I'm increasingly turning towards them for a variety of use-cases, however currently limiting efforts to Chrome due to availability of tools.
Re:Ask HN: Webdevs, designers: what devtools should we (Mozi... by togasystems on Tuesday March 05, 2013 @12:57PM (#5326115)
I second this. I had to create an extension recently and found the entire process a nightmare. Having to use the Venkman debug tool was a large turn off.
Re:Ask HN: Webdevs, designers: what devtools should we (Mozi... by paulrouget on Tuesday March 05, 2013 @12:16PM (#5325764)
We have the inner architecture for "chrome" debugging (extensions debugging). This sill needs some more work though.
Re:Ask HN: Webdevs, designers: what devtools should we (Mozi... by olivierbeaulieu on Tuesday March 05, 2013 @01:38PM (#5326396)
Can we expect improvements to this in the near feature? It would definitely make the idea of making firefox addons more inviting.