Closed
Bug 437078
Opened 17 years ago
Closed 17 years ago
GUIDs not included in bookmark backups
Categories
(Firefox :: Bookmarks & History, defect, P1)
Firefox
Bookmarks & History
Tracking
()
VERIFIED
FIXED
Firefox 3.5
People
(Reporter: dietrich, Assigned: dietrich)
References
Details
(Keywords: fixed1.9.0.2)
Attachments
(1 file)
|
5.60 KB,
patch
|
asaf
:
review+
samuel.sidler+old
:
approval1.9.0.2+
|
Details | Diff | Splinter Review |
The problem with doing this is that when bookmarks are restored, extensions such as Foxmarks and Weave will have lost unique identity across profiles for bookmark items.
I don't know how either extension handles the situation where you have 2 profiles, that are the same, but appear to have never been synced. It's likely that it is painful regardless.
| Assignee | ||
Comment 1•17 years ago
|
||
there is no reason that i can discern for that line of code to be present.
| Assignee | ||
Updated•17 years ago
|
Flags: blocking1.9.0.1?
Priority: -- → P1
Target Milestone: Firefox 3 → ---
Comment 2•17 years ago
|
||
Comment on attachment 323587 [details] [diff] [review]
fix + test
I'm pretty sure the idea behind this check is similar to the one behind the livemark-annotation check - don't get or set "internal" annotations within front-end code (and rather use the apis which expose these annotations, in this case get/setItemGUID). That said, I don't think it's worth changing the data structure in this case, especially now that this file lives in toolkt/.
So, r=mano.
Attachment #323587 -
Flags: review?(mano) → review+
Comment 3•17 years ago
|
||
If this is ready to go, can we get it marked for approval1.9.0.1?
Flags: wanted1.9.0.x+
Flags: blocking1.9.0.1?
Flags: blocking1.9.0.1-
| Assignee | ||
Updated•17 years ago
|
Attachment #323587 -
Flags: approval1.9.0.1?
Updated•17 years ago
|
Attachment #323587 -
Flags: approval1.9.0.1? → approval1.9.0.2?
| Assignee | ||
Comment 4•17 years ago
|
||
changeset: 15657:b96b023e4a43
Status: ASSIGNED → RESOLVED
Closed: 17 years ago
Resolution: --- → FIXED
Target Milestone: --- → Firefox 3.1
Comment 5•17 years ago
|
||
Comment on attachment 323587 [details] [diff] [review]
fix + test
Approved for 1.9.0.2. Please land in CVS. a=ss
Attachment #323587 -
Flags: approval1.9.0.2? → approval1.9.0.2+
| Assignee | ||
Comment 6•17 years ago
|
||
Checking in toolkit/components/places/src/utils.js;
/cvsroot/mozilla/toolkit/components/places/src/utils.js,v <-- utils.js
new revision: 1.21; previous revision: 1.20
done
RCS file: /cvsroot/mozilla/toolkit/components/places/tests/bookmarks/test_restore_guids.js,v
done
Checking in toolkit/components/places/tests/bookmarks/test_restore_guids.js;
/cvsroot/mozilla/toolkit/components/places/tests/bookmarks/test_restore_guids.js,v <-- test_restore_guids.js
initial revision: 1.1
done
| Assignee | ||
Updated•17 years ago
|
Keywords: fixed1.9.0.2
Please see bug 457473 "Bookmark copy creates bookmark with duplicate guid", which was caused by the fix to this bug.
Hello Dietrich, mano, Samuel, and Mike - have you thought about backing this fix out because of the problem it is causing with non-unique guids in bug 457473? Thanks
Updated•17 years ago
|
Status: RESOLVED → VERIFIED
Updated•17 years ago
|
Target Milestone: Firefox 3.1 → Firefox 3.5
Comment 9•16 years ago
|
||
Bug 451915 - move Firefox/Places bugs to Firefox/Bookmarks and History. Remove all bugspam from this move by filtering for the string "places-to-b-and-h".
In Thunderbird 3.0b, you do that as follows:
Tools | Message Filters
Make sure the correct account is selected. Click "New"
Conditions: Body contains places-to-b-and-h
Change the action to "Delete Message".
Select "Manually Run" from the dropdown at the top.
Click OK.
Select the filter in the list, make sure "Inbox" is selected at the bottom, and click "Run Now". This should delete all the bugspam. You can then delete the filter.
Gerv
Component: Places → Bookmarks & History
QA Contact: places → bookmarks
You need to log in
before you can comment on or make changes to this bug.
Description
•