Closed
Bug 978543
Opened 11 years ago
Closed 11 years ago
bookmarks backup can not be processed
Categories
(Firefox :: Bookmarks & History, defect)
Tracking
()
RESOLVED
INCOMPLETE
People
(Reporter: landis, Unassigned)
Details
User Agent: Mozilla/5.0 (X11; Linux i686; rv:30.0) Gecko/20100101 Firefox/30.0 (Beta/Release)
Build ID: 20140301030204
Steps to reproduce:
1) Create Backup.json and Backup.html using Nightly (central)
2) Delete excessive bookmarks
3) ShutDown / Start Nightly
Actual results:
1) Bookmarks Toolbar (personal bar) is AGAIN EMPTY !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
2) Open Library
3) Chose to Restore or Import ( .json or .html) file
4) EVERY 'Backup', since you started making them faster, approximately 10 days are BAD... ERROR: Unable to Process File!!!!!!!!!!!
Expected results:
1) FF should, as advertised, be able to create and restore a backup.
2) This IS Beyond Un-Acceptable!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
STOP messing with the looks of FF and work on the Function! Australis is ugly anyways. The 'menu button' is Retarded! It's neither a button or a menu.
If I wanted google chrome, I'd install and use it and not FF
I just 'cleaned up' my bookmarks... WASTED 2 hours.
This **** has cost me a Hundred Hours of my Life....
Landis.
Comment 1•11 years ago
|
||
You are using nightly which is unstable. If you want to waste less than "hundred hours of your life" you could consider using stable software. You also might want to repair your keyboard, it's printing ten exclamation mark signs instead of one.
(In reply to Landis Reed from comment #0)
> 1) Create Backup.json and Backup.html using Nightly (central)
How exactly? "create X by using Y" is not a clear step that somebody else could follow.
> 2) Delete excessive bookmarks
I have no idea what this step means.
Flags: needinfo?(landis)
Updated•11 years ago
|
Component: Untriaged → Bookmarks & History
Updated•11 years ago
|
Status: UNCONFIRMED → RESOLVED
Closed: 11 years ago
Flags: needinfo?(landis)
Resolution: --- → INCOMPLETE
You need to log in
before you can comment on or make changes to this bug.
Description
•