New issue
Advanced search Search tips

Issue 901351 link

Starred by 1 user

Issue metadata

Status: Assigned
Owner:
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 3
Type: Task



Sign in to add a comment

Better layout for chrome://discards graph view

Project Member Reported by siggi@chromium.org, Nov 2

Issue description

We already have a great many ideas for improving the graph view in Chrome discards. This bug is a dumping ground for those idea.
 
Better base layout:
- Pin pages to a Y coordinate toward the top of the graph.
- Optionally stagger pages towards the top.
- Distribute pages in the X, by biasing or pinning them on an X coordinate.
- Likewise pin processes to a Y coordinate towards the bottom of the graph.
- Bias frames towards a y-coordinate proportional to their level in the frame tree.

Better transitions:
- Initialize nodes to a location proximate to their graph neighbors.
Better data visualization:
- Label page nodes with the page title.
- Label frame nodes with their URL.
- Size process nodes proportionally to their memory size.
- Color process nodes proportionally to their CPU usage.
- Size page and frame nodes proportionally to their estimated memory size.
- Allow presentation of lifecycle state or other interesting attributes by frame or page.
- Allow presentation of current priorities.
Add a selection mode:

- clicking on a node highlights all nodes and edges related to it in a meaningful way?
Better data visualization:
- Propagate the set of hosted sites down to process nodes.
- Provide some kind of a detail view for a selected node.
Status: Assigned (was: Untriaged)
It would be useful to allow "pinning" frame nodes, such that they don't move around when the graph changes around them. This makes it easier to observe how a particular part of the graph changes during navigation or such.

Sign in to add a comment