Skip to content

Instantly share code, notes, and snippets.

@captainbrosset

captainbrosset/backlog.md

Last active September 24, 2018 14:19
Show Gist options
  • Save captainbrosset/b6873dea1eed17c67f60b6a7561fd267 to your computer and use it in GitHub Desktop.
Save captainbrosset/b6873dea1eed17c67f60b6a7561fd267 to your computer and use it in GitHub Desktop.
Download ZIP
webcompat backlog
Raw
backlog.md

Update: webcompat bugs are now tracked in bugzilla, they just all block this meta bug: https://bugzilla.mozilla.org/show_bug.cgi?id=1493094

Below is the list of ideas that don't yet have bugs

  • [Debugger] Nonsensical "steps out". The step out of Firefox devtools seems to be working differently from the one in Chrome. There are many cases where it doesn't seem to make sense. Karl will try to find a practical example
  • [Debugger] Logging all events that are fired for a given period of time
  • [Debugger] being able to set breakpoints on a column+line/specific instruction, not just an entire line.
  • [Debugger] improve the "click this line of a stack trace to jump to that code" feature so it takes you to the column+line in the trace, not just the start of the entire line (for minified scripts).
  • [Debugger] improve the same function so that it uses the pretty-printed version of the script, if one has been opened.
  • [Debugger] being able to modify a bit of script text, and have that version be used upon reload.
  • [Debugger] being able to black-box specific functions/objects, rather than just full source files.
  • [Debugger] being able to know which source file a console.logged function wasv defined in and/or to jump to it.
  • [Debugger] ability to set breakpoints or log stack traces whenever a given object is vaccessed/mutated (whether its a built-in JS object, DOM element, etc).
  • [Debugger] logging whenever a window object changes (for instance due tov document.write) and showing a trace to know what bit of script triggered it.
  • [Debugger] add workers/serviceworkers/extension scripts/etc to the "select whichvdocument the console is working with" feature.
  • [Debugger] Hard to diagnose compat problems when an event is wrapped by a generic handler before being dispatched to the actual function in charge of doing something.
  • [Debugger] Hard to diagnose compat problems when events are caught in a timer loop (do something with this if only in the x ms) aka artificially managing the event queue. We get caught in the event loop and can't go out because the step by step is not fast enough.
  • [Debugger] step by step jumping to the minified code instead of the prettyfied one.
@digitarald
Copy link

[Debugger] Nonsensical "steps out". The step out of Firefox devtools seems to be working differently from the one in Chrome. There are many cases where it doesn't seem to make sense. Karl will try to find a practical example

Pinged @karlcow if this is https://bugzilla.mozilla.org/show_bug.cgi?id=923975

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment