Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

Devtools Perf User Stories

6 views
Skip to first unread message

Jan Odvarko

unread,
Oct 24, 2017, 3:27:47 AM10/24/17
to dev-devel...@lists.mozilla.org
Each Toolbox panel should come up with (up to) the three top interactions
we must focus on and make fast. Please let me know what these interactions
should be (or make a comment in the doc below).

There is already DevTool Perf Program
<https://docs.google.com/document/d/1U_0lNALuyTLQiw5mVfa0rTy4jkvJO2NS5Rio_8ryXyk/edit?ts=59de6e3a#heading=h.92qerz6adgud>
doc (by Harald), that lists some interactions, so you might check if the
current suggestions are accurate.

According to our discussion last week, one of the top interactions for
*every* panel is “Reload the page with the tool open”. But, there might be
others like e.g. "stepping" for the Debugger or "expand request" for the
Net monitor.

Thanks!

Honza


This is the current state (snippet from the doc):


-

Inspector
-

Reload the page with the inspector open
-

Inspect element from Context Menu
-

Change Node
-

Switch to Computed Tab
-

Switch to Rules Tab
-

Console
-

Reload the page with the console open
-

Open empty
-

Open with lots (1000+) cached messages
-

Expand object
-

Clear console
-

Debugger
-

Reload the page with the debugger open
-

Open JS file from Sources
-

Open JS file from Console
-

Hit breakpoint
-

Stepping
-

Pausing
-

Resume
-

Netmonitor
-

Reload the page with the Netmonitor open (very important)
-

Expand resource (important when lazy load introduced)
-

Add resource (not important atm)
-

Clear (not important atm)
-

RDM
-

Reload the page with the RDM open
-

Switch device
0 new messages