Consider support for containers sort order
Categories
(Firefox :: Security, defect, P5)
Tracking
()
People
(Reporter: jkt, Assigned: me)
References
(Blocks 2 open bugs)
Details
(Keywords: dev-doc-complete, Whiteboard: [domsecurity-backlog])
Attachments
(2 files)
Reporter | ||
Updated•8 years ago
|
Comment 1•8 years ago
|
||
Updated•8 years ago
|
Updated•8 years ago
|
Reporter | ||
Comment 2•8 years ago
|
||
Comment 3•7 years ago
|
||
Comment 4•7 years ago
|
||
Reporter | ||
Comment 5•4 years ago
|
||
Depends on D103531
Updated•4 years ago
|
Comment 6•3 years ago
|
||
The bug assignee didn't login in Bugzilla in the last 7 months.
:sgalich, could you have a look please?
For more information, please visit auto_nag documentation.
Updated•3 years ago
|
Comment 7•3 years ago
|
||
(In reply to Konrad Gądek from comment #4)
To maybe state the obvious, the current manual workaround is to open
$PROFILE/containers.json
and reorder array entries.
Thank you. Although the general workaround of "open the profile and change something" might have been obvious, I was unsure what specific file I would have to change.
Now to see if that still works after 5 years of updates and with Mozilla's ever-increasing tech debt...
+1 I've also this issue.
Plus, the order isn't the same in firefox preferences and plugin preferences. Cf https://imgur.com/a/fUjbU19
Updated•2 years ago
|
Updated•2 years ago
|
Comment 9•2 years ago
|
||
The severity field for this bug is relatively low, S3. However, the bug has 10 votes.
:serg, could you consider increasing the bug severity?
For more information, please visit auto_nag documentation.
Comment 10•2 years ago
|
||
The last needinfo from me was triggered in error by recent activity on the bug. I'm clearing the needinfo since this is a very old bug and I don't know if it's still relevant.
Updated•2 years ago
|
Updated•1 year ago
|
Assignee | ||
Comment 11•1 year ago
|
||
- Based off patch by jkt
- Integrate suggestions from robwu (support bulk move, return type, json)
- Add tests for reordering identities
- position is index:
a) in resulting array
b) ignoring non-public identities - No observer notification as no identities were added/removed/modified
- Rob Wu was reviewer on previous patch
(a) is important when moving past current position:
Moving 0 to position=2 in [0 1 2 3] means [1 2 0 3] if position is in
resulting array, but [1 0 2 3] if position is index in starting array.
This is coherent with the interpretation of the tabs.move() parameter
(b) skipping non-public identities means:
Moving 0 to position=2 in [0 * * 1 2 3] (with * private identities)
results in [* * 1 2 0 3] and not [* * 0 1 2 3]
Updated•1 year ago
|
Comment 12•10 months ago
|
||
I'm putting dev-doc-needed here so that the feature can be documented on MDN: a new article for contextualIdentities.move, BCD entry and developer release notes.
I'll reach out to our tech writer (Richard) to make sure that he can see this bug despite it not being in the WebExtensions product.
Comment 13•10 months ago
|
||
Comment 14•10 months ago
|
||
bugherder |
Updated•10 months ago
|
Description
•