Closed
Bug 1212297
Opened 9 years ago
Closed 9 years ago
Chrome bookmarks migration doesn't drops errors on the floor, and should ignore Chrome's chrome:// URLs
Categories
(Firefox :: Migration, defect)
Firefox
Migration
Tracking
()
VERIFIED
FIXED
Firefox 44
Tracking | Status | |
---|---|---|
firefox44 | --- | verified |
People
(Reporter: Gijs, Assigned: Gijs)
References
Details
Attachments
(1 file)
The insertBookmarkItems thing just Cu.reportError's everything, and then the callback gets called with true.
The reason I was seeing errors was that the bookmarks in Chrome included:
chrome://bookmarks/
which we don't consider a valid chrome:// URLs.
I think we should just ignore all chrome:// URLs we get in the migration. I also think the error reporting should be better, not least for the sake of bug 731025 (which currently wouldn't flag up issues encountered in insertBookmarkItems, like the crazy URLs we saw for IE in bug 1194692).
I have a patch.
Assignee | ||
Comment 1•9 years ago
|
||
Bug 1212297 - improve error handling in Chrome bookmarks migration code, r?MattN
Attachment #8670749 -
Flags: review?(MattN+bmo)
Assignee | ||
Updated•9 years ago
|
Assignee: nobody → gijskruitbosch+bugs
Status: NEW → ASSIGNED
Comment 2•9 years ago
|
||
Comment on attachment 8670749 [details]
MozReview Request: Bug 1212297 - improve error handling in Chrome bookmarks migration code, r?MattN
https://reviewboard.mozilla.org/r/21449/#review19325
::: browser/components/migration/ChromeProfileMigrator.js:62
(Diff revision 1)
> + if (item.url.trim().startsWith("chrome:")) {
> + // Skip invalid chrome URIs. Creating an actual URI always reports
> + // messages to the console, so we avoid doing that.
> + continue;
> + }
I thought we already fixed handling chrome: URIs in another bug but maybe it never got fixed.
Attachment #8670749 -
Flags: review?(MattN+bmo) → review+
Comment 4•9 years ago
|
||
Status: ASSIGNED → RESOLVED
Closed: 9 years ago
Resolution: --- → FIXED
Target Milestone: --- → Firefox 44
Updated•9 years ago
|
Flags: qe-verify+
Comment 5•9 years ago
|
||
I was able to reproduce this issue on Firefox 43.0.4 (20160105164030) under Mac OS X 10.10.5.
Verified fixed on Firefox 44 beta 8 (20160111185352) under Mac OS X 10.10.5, Windows 10 64-bit and Ubuntu 14.04 32-bit.
You need to log in
before you can comment on or make changes to this bug.
Description
•