iDevie
November 2021
M T W T F S S
1234567
891011121314
15161718192021
22232425262728
2930  

Categories


There’s sometimes a tribal attitude about how web developers should be debugging their code and solving problems. There’s the console.log loyalists, then there’s the debugger/breakpoint maximalists. I worked on the Firefox DevTools debugger for years and I can tell you my philosophy — use whichever tool helps you get the job done!

I use console.log for very simple problems, other times when I want an audit trail I can analyze after a series of events to spot the problem and share with others. I use breakpoints when I want to halt execution to to see values and the visual state of the UI. One tool you can use to get the best of both worlds is logpoints, a breakpoint-like mechanism in the devtools debugger that logs instead of halts!

To add a logpoint:

  • open the devtools debugger
  • right-click a line number in a JavaScript file,
  • provide the log message accompanied by any variables you’d like in the log:
  • MooTools Window Object Dumping

    MooTools Window Object Dumping

    Ever want to see all of the information stored within the window property of your browser? Here’s your chance. The XHTML We need a wrapper DIV that we’ll consider a console. The CSS I like making this look like a command-line console. The MooTools JavaScript Depending on what you have loaded…

  • GitHub-Style Sliding Links

    GitHub-Style Sliding Links

    GitHub seems to change a lot but not really change at all, if that makes any sense; the updates come often but are always fairly small. I spotted one of the most recent updates on the pull request page. Links to long branch…

<!– –>

Comments 0
There are currently no comments.