Open
Bug 1676180
Opened 5 years ago
Updated 2 years ago
Topsite loses pin after reorganized and jumps position
Categories
(Firefox :: Top Sites, defect, P2)
Tracking
()
NEW
| Tracking | Status | |
|---|---|---|
| firefox-esr78 | --- | unaffected |
| firefox82 | --- | unaffected |
| firefox83 | --- | wontfix |
| firefox84 | --- | wontfix |
| firefox85 | --- | affected |
People
(Reporter: muirpablo, Unassigned)
References
(Blocks 2 open bugs)
Details
Attachments
(1 file)
|
155.79 KB,
image/jpeg
|
Details |
[Suggested Severity:]
S3
[Description:]
When all topsites have a pin, if i move one of them, then another topsites looses its pin status and also jumps the order
[Environment:]
MacOS 10.14
83.0b10-trybuild
[Preconditions:]
Reorganize all topsites so each has a pin
[Steps:]
- Download and install RO localized Firefox.
- Create an user.js and set: browser.topsites.useRemoteSetting = true and browser.search.region to "RO", connecting to the staging main-preview.
- Start the browser with the predefined profile.
- Open a new tab.
- Reorganize all topsites so each one has a pin icon
- Move a topsite town (on screenshot i moved example8 topsite down.
- Watch topsite position 5 and position 6
[Actual Result:]
Pinned topsite position 6 looses its pin and moves to position 4
Topsite position 6 jumps order of position 5 and goes to position4
[Expected Result:]
Topsite position 5 should move to position 4 pinned
Topsite position 6 should move to position 5 pinned
screenshot attached, showing that:
- amazon lost its pin
- amazon jumped ebay order
Updated•5 years ago
|
status-firefox-esr78:
--- → unaffected
Updated•5 years ago
|
Comment 1•5 years ago
|
||
The severity field is not set for this bug.
:dao, could you have a look please?
For more information, please visit auto_nag documentation.
Flags: needinfo?(dao+bmo)
Updated•5 years ago
|
Severity: -- → S3
Flags: needinfo?(dao+bmo)
Priority: -- → P2
Updated•5 years ago
|
status-firefox85:
--- → affected
Updated•5 years ago
|
You need to log in
before you can comment on or make changes to this bug.
Description
•