#Firefox developer edition 39 code

Now I know its not fair to make a judgement based on a single bug, too many variables at play etc but the lesson I learnt as a stressed out, time-pressured developer is not to ever ever ever use a browser that wasn't the standard version of a browser for development, the one most likely to be used by the client or end-user. It was driving me mad.Īfter an hour or so of frustration I realised that the bug did not occur on Chrome or Firefox 'Standard' Editions and was only occuring on Firefox Developer Edition.

I was presented with a very weird UI bug from the client that I could not reproduce whatsoever. This comes from a place of love, and I'll still always use FF over Chrome, but I really have to ask if anyone else experiences the same issues, or if it's perhaps my setup/code that causes the problems?Ī few years ago, while working at an agency, I was using the Firefox Developer Edition to build the front-end for a website.

#Firefox developer edition 39 code

A few examples I frequently experience:ġ) Stepping through TS frequently switches back to the source JS.Ģ) Breakpoints don't always go away, and sometimes a page reloads with an invisible breakpoint, that stops the code, but doesn't show up in the list of breakpoints, and doesn't seem to be removable.ģ) Breakpoints don't always stop at the the right place.Ĥ) After having the tools open for a while, the tab starts freezing for multiple seconds every few seconds (GC, according to the perf tab, so it's either my code or the dev tools)

It's something I noticed especially when they switched to React. You know, I've been using Firefox Dev Edition since it was Firefox Aurora (or Beta, I guess?), and it's great to hear that they are improving the dev tools! But I have to ask this in the nicest way possible: does anyone else think the tools just don't work a lot of the time?