Open
Bug 689377
Opened 13 years ago
Updated 2 years ago
Adding device re-ordered bookmarks toolbar
Categories
(Firefox :: Sync, defect)
Firefox
Sync
Tracking
()
NEW
People
(Reporter: fligtar, Unassigned)
References
(Blocks 1 open bug)
Details
(Whiteboard: [sync:bookmarks])
Attachments
(3 files)
I just added my Galaxy Tab to my Sync account, and the bookmarks in my Bookmarks Toolbar on my laptop (Aurora 8) are now all out of order.
Comment 1•13 years ago
|
||
Justin, which version of Fennec are you running on the Galaxy? Can you provide sync logs from both devices? See https://philikon.wordpress.com/2011/06/13/how-to-file-a-good-sync-bug/ Thanks!
Component: Firefox Sync: UI → Firefox Sync: Backend
QA Contact: sync-ui → sync-backend
Reporter | ||
Comment 2•13 years ago
|
||
I'm running a nightly I downloaded today.
Reporter | ||
Comment 3•13 years ago
|
||
Comment 4•13 years ago
|
||
(In reply to Justin Scott [:fligtar] from comment #3) > Created attachment 562592 [details] > sync-log from laptop Are there any previous logs listed? A dump of $profile/weave/log would be informative.
Reporter | ||
Comment 5•13 years ago
|
||
Sorry for the lag -- hectic week. Here's a zip of my logs from the laptop. Note that I only turned on success logging after filing this bug.
Comment 6•12 years ago
|
||
Possibly a dupe of 708149. Justin, do you have things like smartmarks, livemarks, feeds or separators on your BM toolbar? If so, look in your library. Did all those things get pushed to the end of the BM Toolbar folder?
Comment 7•12 years ago
|
||
(In reply to Tracy Walker [:tracy] from comment #6) > Possibly a dupe of 708149. Tracy: Android Sync didn't exist in September. This was a XUL Fennec (JS Sync) bug.
Comment 8•12 years ago
|
||
me is sometimes time/services continuum challenged. :-)
Updated•12 years ago
|
Blocks: bookmarksync
Whiteboard: [sync:bookmarks]
Assignee | ||
Updated•6 years ago
|
Component: Firefox Sync: Backend → Sync
Product: Cloud Services → Firefox
Updated•2 years ago
|
Severity: normal → S3
You need to log in
before you can comment on or make changes to this bug.
Description
•