Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Firefox Debugger

mozilladevelopers.github.io

Post reply on HN
Print view View original

51–60 of 70 posts

Re: Firefox Debugger

#53

Post by a_humean »

wyattjoh wrote: post #52

Wish I didn't have to open Chrome to view websocket frames though. Firefox does detect that a WS connection was made, it just can't inspect it.

This is also a big barrier for me using firefox in development, and pre-v57 Firefox used to have an extension for websockets that was nice, but its gone now with the new web extension APIs.

Re: Firefox Debugger

#54

Post by shmerl »

deltaprotocol wrote: post #49
shmerl wrote: post #34

Earlier quoted context omitted.

Compare this new dark to one that was there a few versions back. I'm talking about the older one. Example: https://support.cdn.mozilla.net/media/uploads/images/2016-09...

Fully agree with you. The old dark theme feels more comfortable (less contrast between colors). Each and every time I open the devtools now this thought crosses my mind.

I suppose we should file a bug about bringing it back.

Re: Firefox Debugger

#55

Post by beavis2 »

pjmlp wrote: post #4
melicerte wrote: post #2

Sad to see a post by Mozilla only referencing Mac and Windows shortcuts to start the debugger. Most of the web developers I know are using Linux for web development, including javascript (some are using MacOS, none Windows). On Ubuntu, the debugger is started by using S (like Windows actually).

I don't know any Web developers using Linux on their desktops, as company policy requires Windows desktops. Linux is only used for Java based backends, when deploying into production. With .NET deployments being done on IIS, even with .NET Core. Some of the designers are using Photoshop on macOS. Anecdote data.

At companies that let you decide for yourself (I've worked at 4), it's Mac and Linux. Windows is rare.. but there's usually one or two. Different IDEs. Just use whatever your more comfortable/efficient with.

Admin use Windows, Mac is rare.

I find it strange, in this day and age, being forced to use a single OS because "policy", especially when developing for an "open platform".

Re: Firefox Debugger

#56

Post by vanderZwan »

wyattjoh wrote: post #52

Wish I didn't have to open Chrome to view websocket frames though. Firefox does detect that a WS connection was made, it just can't inspect it.

I have a similar thing but with profiling JS performance: if you profile a page in Chrome and then inspect the source code, it gives estimates of seconds spent per line of code. Firefox does not have this.

Being able to detect which function is the bottleneck is great, but being able to then figure out where the time is spent inside that function can be very enlightening too.

Re: Firefox Debugger

#57

Post by Groxx »

masklinn wrote: post #20

Here's something which is still missing from both Firefox and Chrome debuggers: "tracing" breakpoints. That's one of the few nice/advanced features from Xcode and Safari, aside from making a breakpoint conditional you can: * skip it the first n times (default: 0) * make it non-breaking * associate various actions which are executed if the breakpoint "triggers" (the condition matches) even if the breakpoint is non-bre…

Conditional breakpoints have been around for years, which solve all of those via arbitrary javascript. You just make the condition falsey if you don't want it to break (or `doAnything() && false`). Skip-counters are just a global counter and `x++ > N`. "Probe Expression" does look pretty neat though, that'd be a bit of a pain to do by hand (probably just viewing logs, which does provide rich objects in recent-ish years).

Granted, the UI isn't as clear about the capabilities, but I generally prefer "run JS, return true" over "choose one of N kinds of things to do", even if one of the N is "run JS, return true". Minus skip counters, those are a bit annoying by hand (needing globally unique var names and all).

I'm not sure when Firefox's built-in debugger got it, but I see search results implying they've been part of FireBug since 2007 at the very least. And I don't remember Chrome's debugger ever not having it (once they got their current-gen-like one, iirc it launched with extremely limited devtools?), though I could easily be forgetting the early days.

Re: Firefox Debugger

#58

Post by sudeepto_dutta »

callahad wrote: post #26
polack wrote: post #24

Slightly OT; What's the "Developer Edition"? > Build, test, scale and more with the only browser built just for developers. This is the only description I could find on their website. What's the difference to the normal version?

DevEdition is our fourth release channel, along with Stable, Beta, and Nightly builds. The engine is generally based on Beta, but we can ship features to DevEdition separately from mainline Firefox. For example, we can ship new developer tools to that channel before they land in Beta, it runs in its own separate profile by default, we allow Developer Edition to disable the add-on signing requirement, etc.

Hello Sir,

Pardon me if this is a silly question, but in the about:config page of Firefox Developer Edition the value for app.update.channel is aurora. But AFAIK, the aurora channel was stopped since April 18th of this month.

This is the screenshot : https://imgur.com/r5Kcqb3

Re: Firefox Debugger

#59

Post by KwanEsq »

sudeepto_dutta wrote: post #58
callahad wrote: post #26

Earlier quoted context omitted.

DevEdition is our fourth release channel, along with Stable, Beta, and Nightly builds. The engine is generally based on Beta, but we can ship features to DevEdition separately from mainline Firefox. For example, we can ship new developer tools to that channel before they land in Beta, it runs in its own separate profile by default, we allow Developer Edition to disable the add-on signing requirement, etc.

Hello Sir, Pardon me if this is a silly question, but in the about:config page of Firefox Developer Edition the value for app.update.channel is aurora. But AFAIK, the aurora channel was stopped since April 18th of this month. This is the screenshot : https://imgur.com/r5Kcqb3

The aurora tree/part of the release cycle has gone away, but dev edition needs a separate update channel from beta, and was already using "aurora", so it was obviously less work to keep the name around just for the channel rather than rename it (and that might have prevented keeping existing dev edition users getting updates)

(So the _channel_ didn't actually ever go away, it just changed which tree it drew from)

(Tree being synonymous with "code repository" throughout this comment)

Re: Firefox Debugger

#60

Post by callahad »

sudeepto_dutta wrote: post #58
callahad wrote: post #26

Earlier quoted context omitted.

DevEdition is our fourth release channel, along with Stable, Beta, and Nightly builds. The engine is generally based on Beta, but we can ship features to DevEdition separately from mainline Firefox. For example, we can ship new developer tools to that channel before they land in Beta, it runs in its own separate profile by default, we allow Developer Edition to disable the add-on signing requirement, etc.

Hello Sir, Pardon me if this is a silly question, but in the about:config page of Firefox Developer Edition the value for app.update.channel is aurora. But AFAIK, the aurora channel was stopped since April 18th of this month. This is the screenshot : https://imgur.com/r5Kcqb3

Aurora used to be a separate pre-beta, post-nightly release channel:

    Release
In 2014, we rebranded Aurora builds to "Developer Edition" to give it better visibility and ship experimental features that we thought would be interesting to web and add-on developers.

Earlier this year, we sped up our time-to-release by removing Aurora from the pipeline, but we kept it as a separate channel roughly at parity with Beta:

    Release
Which is where things are today.
Post reply on HN