Closed
Bug 1661552
Opened 4 years ago
Closed 4 years ago
Sorting about:processes by Name sorts only the subitems
Categories
(Core :: DOM: Content Processes, defect, P3)
Core
DOM: Content Processes
Tracking
()
Tracking | Status | |
---|---|---|
firefox82 | --- | fixed |
People
(Reporter: itiel_yn8, Assigned: Yoric)
References
Details
Attachments
(1 file)
STR:
- Open about:processes
- Click the Name column header once -- the separators are gone (not sure if intentionaly or not), and the top-level item names are not actually sorted
- Expand any top-level item and sort by name -- the subitems are being sorted, and not the top-level ones
Updated•4 years ago
|
Severity: -- → S3
Fission Milestone: --- → M7
Priority: -- → P3
Summary: Sorting by Name sorts only the subitems → Sorting about:processes by Name sorts only the subitems
Assignee | ||
Comment 1•4 years ago
•
|
||
Oh, right. That's going to be a bit tricky to solve.
Names used to be computed in aboutProcesses.js but they're now outsourced to Fluent.
So I see the following options:
- Compute the names twice, once for sorting and once for display.
- Adopt an approximation in which we actually sort by origin rather than by alphanumerical order.
- Call Fluent much earlier to determine names way before we need to display them (or before we even know whether we'll need to display them).
Assignee | ||
Comment 2•4 years ago
|
||
Sorting by name used to work because we computed the display name of each process within aboutProcesses.js. These days, fluent does the job, so this doesn't work anymore.
This patch approximates sorting by name with sorting by origin.
Updated•4 years ago
|
Assignee: nobody → dteller
Status: NEW → ASSIGNED
Pushed by dteller@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/ac4c876a2e1d
In about:processes, sorting by name now sorts by origin;r=florian
Comment 4•4 years ago
|
||
bugherder |
Status: ASSIGNED → RESOLVED
Closed: 4 years ago
status-firefox82:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → 82 Branch
You need to log in
before you can comment on or make changes to this bug.
Description
•