1916596 - Synchronization of separators

Status: RESOLVED INACTIVE

(Firefox :: Sync, enhancement)

Description

[Karel Tomanec]

Attachment: sync_problem.png

User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:130.0) Gecko/20100101 Firefox/130.0

Steps to reproduce:

Set bookmarks and separators and synced my browser settings on another device.

Actual results:

The all separators are positioned at the end of bookmarks on the synced device.

Expected results:

Separators should have remained at the original positions.

Comment 1

[Mark Hammond [:markh] [:mhammond]]

This is surprising as we do sync the position of the separators. If you are able to reproduce this in a new temporary profile on Desktop, then getting access to the sync logs for that would be interesting. If you can, the best thing is probably to install the about:sync addon (https://addons.mozilla.org/en-US/firefox/addon/about-sync/) before connecting to sync and grabbing the logs from that. Feel free to ping us here if that's something you are able to do.

Comment 2

[Timea Zsoldos [:tzsoldos], Desktop QA]

I have tested your issue on the Nightly build 132.0a1 (2024-09-04), on latest Nightly build 133.0a1 (2024.10.27) and could not reproduce it using Windows 10.
If the issue is still reproducible on your end, can you please retest this using the latest Nightly build (https://nightly.mozilla.org/) using a new clean Firefox profile (https://goo.gl/AWo6h8) to eliminate the potential causes?
Also please attach the about:support here (go to about:support, click on "Copy test to clipboard" and paste it here).
Thank you!

Comment 3

[BugBot [:suhaib / :marco/ :calixte]]

Redirect a needinfo that is pending on an inactive user to the triage owner.
:lougenia, could you have a look please?

For more information, please visit BugBot documentation.

Comment 4

[Lougenia Bailey]

:ktomanec Thanks again for reporting this issue, but we are unable to determine the cause of the problem without the requested information. If you are able to provide this information, please just add a comment in this bug with that information and we'll get back to you as soon as we can, but in the meantime we are closing this bug so we can focus on the issues which we can address.