Legacy vs RS top-sites order differences after unpinned amazon
Categories
(Firefox :: Top Sites, task, P5)
Tracking
()
| Tracking | Status | |
|---|---|---|
| firefox-esr78 | --- | unaffected |
| firefox86 | --- | unaffected |
| firefox87 | --- | fixed |
| firefox88 | --- | fixed |
People
(Reporter: aflorinescu, Assigned: dao)
References
(Blocks 1 open bug)
Details
Comparing the unpinned amazon RS top-sites configuration with the legacy configuration , there are a few differences as highlighted here.
Summary:
region US:
RS default unpinned position is 5, legacy had 3
region DE:
RS default unpinned position is 1, legacy had 3
region GB:
RS default unpinned position is 1, legacy had 4
region FR:
RS default unpinned position is 1, legacy had 4
|
Assignee | |
Comment 1•5 years ago
|
||
dao: I'm confused by that bug because amazon should be pinned by default in these regions. can you please clarify?
aflorinescu: so, when you unpin the @amazon it moves to the position specified by the remote settings
dao: okay, I can adjust this in RS but I don't think we really care about this
|
|
Assignee | |
Comment 2•5 years ago
|
||
Made the necessary remote setting changes in main-preview on STAGE and PROD, awaiting review.
|
Reporter | |
Comment 3•5 years ago
|
||
As per :dao, changes are approved on prod, but are not considered cirtical priority, so waiting for the next dump update to verify them.
|
|
Reporter | |
Comment 4•4 years ago
|
||
The verification here was related to the migration from legacy to RS, which has been verified and live for many versions. Not sure why I left this pending and unmarked at that time, cleaning up NIs.
Description
•