Firefox Debugger • Hacker News Board

Re: Firefox Debugger

#21

Post by pjmlp » Tue, Nov 28, 2017, 1:05 PM UTC

bkor wrote: post #13

pjmlp wrote: post #10

Earlier quoted context omitted.

That was my point, each one has a different OS scenario depending where in the world we live on, the policies at workplace and customer sites.

If someone says that Linux should be included and mentions he knows a lot of web developers using Linux, then his added comment is relevant. Windows instructions were already included so your reply wasn't needed and I assume you didn't understand the Linux reply.

I took it as Web devs only use Linux kind of.

Re: Firefox Debugger

#22

Post by bovine3dom » Tue, Nov 28, 2017, 1:13 PM UTC

yorwba wrote: post #3

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).

Are there any shortcuts on Linux which are different from those on Windows by default?

Opening the downloads window is bound to on one and on the other. I can never remember which is which.

Re: Firefox Debugger

#23

Post by 10000100001010 » Tue, Nov 28, 2017, 1:14 PM UTC

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…

You can at least both "Log Message" and "Evaluate" in Chrome with conditional break points. Calling console.log is falsy, so calling it from conditional break points just causes it to log the message (you also have access to any variables in scope of the breakpoint that you can use to build the message). You can do the same thing with executing random JavaScript. Just put the statement and add && false to make sure it always returns false.

Re: Firefox Debugger

#24

Post by polack » Tue, Nov 28, 2017, 1:24 PM UTC

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?

Re: Firefox Debugger

#25

Post by agumonkey » Tue, Nov 28, 2017, 1:32 PM UTC

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?

dark theme... and maybe more

Re: Firefox Debugger

#26

Post by callahad » Tue, Nov 28, 2017, 1:33 PM UTC

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.

Re: Firefox Debugger

#27

Post by ChrisSD » Tue, Nov 28, 2017, 1:37 PM UTC

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…

I get your point but a non-breaking breakpoint sounds like a contradiction. Maybe it should be called a tracepoint?

Re: Firefox Debugger

#28

Post by [deleted] » Tue, Nov 28, 2017, 1:38 PM UTC

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?

[deleted]

Re: Firefox Debugger

#29

Post by neoeldex » Tue, Nov 28, 2017, 1:39 PM UTC

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?

The developer edition is bit more bleeding edge than beta, but less than nightly. Nightly is updated daily. I'm not sure what the developer frequency is. But if your sporting it, you're getting the fresh features not entirely ready.

Re: Firefox Debugger

#30

Post by JeanMarcS » Tue, Nov 28, 2017, 1:40 PM UTC

Since version 57 I have a strange behavior in the debugger (debian 9) : there is a line difference between where I click and the line selected. For a breakpoint I have to click the line above, idem for getting var values.