User:GijsKruitbosch/JS Debugging/Tasks: Difference between revisions

User:GijsKruitbosch/JS Debugging/Tasks (view source)

812 bytes added , 15 June 2006

Confirmed users

455

edits

@@ Line 175: / Line 175: @@
          </tr>
      </table>
+I would probably order these things higher:
+* immediate profiling
+* newlines in watches view (but there's no watch support yet, so?)
+* eval JS in tab/frame/etc.
+And these things lower:
+* JS 1.7
+* inline function editing
+But I think you're generally on the right track.  I need to write here how we can track what document an error came from without biting off everything that's in the current bug 228205, too.  Basically involves finding the current document (via cx->contextPrivate->scriptOwner->frameElement or some such) from the handler called for exceptions and errors, and keeping track of it.  We could also "just" have the console error object QI to nsIException, but I bet that would make some people API-sad, so I'm interested in us keeping the hacks to our side of the line if we can.
+-- shaver