DevTools: indicate which console messages come from service workers (different contexts) |
||||||
Issue descriptionSimilar to the way that timestamps appear to the left of a console message to indicate when it was logged, we should also put the name of the service worker from which it originates.
,
Jan 11 2017
,
Jan 12 2017
,
Jan 13 2017
Update: we can truncate names if they are too long, show a tooltip of the origin on hover, and hide the label if it matches the current context.
,
Jan 18 2017
,
Jan 19 2017
Updated screenshot with: - smaller width labels - gear icon for workers
,
Jan 21 2017
,
Jan 26 2017
Another proposal with only 3 icons: - Gear, workers - Box, non-main frames (same icon used in Application) - Puzzle piece, extensions - no icon for other contexts (top, page, DevTools generated) On hover, we can show the full name of the context. If it's associated with an execution context, we can click the icon to show messages just from that context (changes the context selector dropdown and turns off 'Show all messages'). chowse, dgozman, WDYT?
,
Jan 27 2017
Some more screenshots.
,
Jan 28 2017
,
Feb 2 2017
As a first step, I'd like to land a patch to introduce deterministic ordering for icons. Before after screenshots below
,
Feb 2 2017
Can we move the repeated counter to the left as well?
,
Feb 2 2017
Since the repeat counter can grow arbitrarily longer than the regular error/warning level icons, it would push the group nesting markers to the right and break the vertical group. Either we have error/warning icons to the right of the nesting markers or the repeat counter has to be on the other side from them.
,
Feb 2 2017
Let's explore capping counter to certain width? How does that look?
,
Feb 2 2017
Neat idea! With the repeat capped to 99+, some space is added to the left of every message, which doesn't look bad imo.
,
Feb 2 2017
I don't think capping to 99+ is a good idea - I always want to know if/when it grows. Also, I think we should rework our repeat counter anyways.
,
Nov 8 2017
Now that better filtering options exist: "url:sw.js" and open console sidebar > click "sw.js", this issue is addressed. Closing since no work is currently planned. |
||||||
►
Sign in to add a comment |
||||||
Comment 1 by l...@chromium.org
, Jan 11 201757.3 KB
57.3 KB View Download
87.5 KB
87.5 KB View Download
126 KB
126 KB View Download