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

Fixing shaver's nits, fixing my own commentary, fixing backend-needed listings
(Fixing shaver's nits, fixing my own commentary, fixing backend-needed listings)
Line 30: Line 30:
         <tr>
         <tr>
             <td>3</td>
             <td>3</td>
             <td>Backend for nsIScriptError to report the document an error came from - <strong>Wait... this will probably be too big/complicated to get right on 1.8...</strong></td>
             <td>Make the originated document accessible from any error in the console</td>
             <td>Yes</td>
             <td>No?</td>
             <td>bug 228205</td>
             <td>bug 228205</td>


Line 38: Line 38:
         <tr>
         <tr>
             <td>4</td>
             <td>4</td>
             <td>Frontend adapted to keep breakpoints and such separate on a per-document basis (see above)</td>
             <td>Frontend adapted to keep breakpoints and such separate on a per-document basis (for Firebug's console) (see above)</td>
             <td>Yes</td>
             <td>No?</td>
             <td>bug 228205</td>
             <td>bug 228205</td>


Line 47: Line 47:
             <td>5</td>
             <td>5</td>
             <td>Be able to go from a var referencing a DOM element to that DOM element in DOMI</td>
             <td>Be able to go from a var referencing a DOM element to that DOM element in DOMI</td>
             <td>Yes?</td>
             <td>No?</td>
             <td>-</td>
             <td>-</td>


Line 62: Line 62:
         <tr>
         <tr>
             <td>7</td>
             <td>7</td>
             <td>Changing variable values / evaluating js shouldn't require changing tabs away from the debugger (in Firebug)</td>
             <td>Newlines are lost in the watches view.</td>
             <td>No</td>
             <td>No</td>
             <td>-</td>
             <td>-</td>
Line 70: Line 70:
         <tr>
         <tr>
             <td>8</td>
             <td>8</td>
             <td>Anonymous functions should not be lumped together in profiling.</td>
             <td>Changing variable values / evaluating js shouldn't require changing tabs away from the debugger (in Firebug)</td>
             <td>Presumably not</td>
             <td>No</td>
             <td>-</td>
             <td>-</td>


Line 78: Line 78:
         <tr>
         <tr>
             <td>9</td>
             <td>9</td>
             <td>Newlines are lost in the watches view.</td>
             <td>Evaluate js in different windows/tabs/iframes</td>
 
             <td>No</td>
             <td>No</td>
             <td>-</td>
             <td>-</td>
             <td>None yet</td>
             <td>None yet</td>
         </tr>
         </tr>
         <tr>
         <tr>
             <td>10</td>
             <td>10</td>
             <td>Double-check handling of about:blank and (related) running/stopped state tracking in Firebug.</td>
             <td>Provide immediate access to profiling data</td>
 
             <td>No</td>
             <td>No</td>
             <td>-</td>
             <td>-</td>
             <td>None yet</td>
             <td>None yet</td>
         </tr>
         </tr>
         <tr>
         <tr>
             <td>11</td>
             <td>11</td>
             <td>JS 1.7 improvements</td>
             <td>Anonymous functions should not be lumped together in profiling.</td>
             <td>Yes?</td>
             <td>Presumably not</td>
            <td>-</td>


            <td>-</td>
             <td>None yet</td>
             <td>None yet</td>
         </tr>
         </tr>
         <tr>
         <tr>
             <td>12</td>
             <td>12</td>
             <td>Figure out why I'm crashing on GMail with firebug enabled (hack/sneak/workaround?)</td>
             <td>Double-check handling of about:blank and (related) running/stopped state tracking in Firebug.</td>
            <td>No</td>
            <td>-</td>


            <td>Hopefully not.</td>
            <td>-</td>
             <td>None yet</td>
             <td>None yet</td>
         </tr>
         </tr>
         <tr>
         <tr>
             <td>13</td>
             <td>13</td>
             <td>Provide immediate access to profiling data</td>
             <td>Figure out why I'm crashing on GMail with firebug enabled (hack/sneak/workaround?)</td>


             <td>No</td>
             <td>Hopefully not.</td>
             <td>-</td>
             <td>-</td>
             <td>None yet</td>
             <td>None yet</td>
Line 120: Line 120:
         <tr>
         <tr>
             <td>14</td>
             <td>14</td>
             <td>Evaluate js in different windows/tabs/iframes</td>
             <td>Fix wrapping of variable/value tree</td>


             <td>No</td>
             <td>No</td>
Line 128: Line 128:
         <tr>
         <tr>
             <td>15</td>
             <td>15</td>
             <td>Fix wrapping of variable/value tree</td>
             <td>JS 1.7 improvements</td>
            <td>Yes?</td>


            <td>No</td>
             <td>-</td>
             <td>-</td>
             <td>None yet</td>
             <td>None yet</td>
Line 136: Line 136:
         <tr>
         <tr>
             <td>16</td>
             <td>16</td>
             <td>Inline editing of functions etc.</td>
             <td>Debug mutation events (watch DOM elements)</td>


             <td>No, hopefully.</td>
             <td>Yes</td>
             <td>-</td>
             <td>-</td>
             <td>None yet</td>
             <td>None yet</td>
Line 144: Line 144:
         <tr>
         <tr>
             <td>17</td>
             <td>17</td>
             <td>Debug mutation events (watch DOM elements)</td>
             <td>Getters / Setters improvements</td>


             <td>Yes</td>
             <td>Yes?</td>
             <td>-</td>
             <td>-</td>
             <td>None yet</td>
             <td>None yet</td>
Line 152: Line 152:
         <tr>
         <tr>
             <td>18</td>
             <td>18</td>
             <td>Getters / Setters improvements</td>
             <td>'real' stack list (not a dropdown)</td>


             <td>Yes?</td>
             <td>No</td>
             <td>-</td>
             <td>-</td>
             <td>None yet</td>
             <td>None yet</td>
Line 160: Line 160:
         <tr>
         <tr>
             <td>19</td>
             <td>19</td>
             <td>'real' stack list (not a dropdown)</td>
             <td>Inline editing of functions etc.</td>


             <td>No</td>
             <td>No, hopefully.</td>
             <td>-</td>
             <td>-</td>
             <td>None yet</td>
             <td>None yet</td>
Line 175: Line 175:
         </tr>
         </tr>
     </table>
     </table>
== Getting to the document that error X originated from ==
Shaver should write this sometime (see below)
== Discussion ==


I would probably order these things higher:
I would probably order these things higher:
Line 190: Line 196:


-- shaver
-- shaver
: Done, I think. [[User:GijsKruitbosch|GijsKruitbosch]] 07:20, 16 June 2006 (PDT)
Confirmed users
290

edits