Changes between Initial Version and Version 1 of StateofWebInspector2016


Ignore:
Timestamp:
Oct 26, 2016 1:13:40 PM (7 years ago)
Author:
Jon Davis
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • StateofWebInspector2016

    v1 v1  
     1- Web Inspector turned 10 years old this year.
     2- Evolution of the web inspector:
     3  1. Very basic, show DOM tree, floating HUD window. Limited: no debugger, couldn't show source, etc.
     4  2. Debugger in separate application. But still limited.
     5  3. Resources view.
     6  4. Integrated debugger into actual inspector.
     7  5. Introduced the timeline view into inspector.
     8  6. Current web inspector: Tab bar UI. Like this UI because it scales well to newer features/designs.
     9
     10- Debugger improvements:
     11 - Many changes are in Safari Technology Preview.
     12 - New global breakpoint for console.assert
     13 - When stopped on a breakpoint, highlight the expression that is about to execute.
     14 - Can also go up the call chain to see how we got to the top frame. Show caller with highlighting.
     15 - Can now set breakpoints on comments/empty lines and it will slide to next statement to execute.
     16 - (Questions on how default parameter values interact with the debugger.)
     17
     18- Splitting type profiler from code coverage profiler
     19 - Used to just be the type profiler to toggle both
     20 - Now we have individual buttons for each profiler
     21 - In Safari Technology Preview.
     22
     23- Heap map view:
     24 - Idea to highlight where time is spent.
     25 -
     26
     27- Web Inspector Testing:
     28 - Test suite for writing async inspector tests.
     29 - New top-level uncaught exception view in engineering builds for inspector. Easily create bugzilla from call trace.
     30 - Wanting to be able to inspect layout tests.
     31 - UI testing for the inspector:
     32   - Need some isolation between tests and how the inspector is implemented.
     33   - Ideas: Every view in the inspector has a wrapper object. Must be able to simulate user interaction that isn't tied to the DOM layout.
     34   - Wrapper objects that wrap UI widgets. Allows for a simplified UI.
     35   - Clicks/typing will re-use ability added for web driver to simulate actions as if it was a user doing it.
     36