Beginning on October 25th, 2016, Persona will no longer be an option for authentication on BMO. For more details see Persona Deprecated.
Last Comment Bug 647399 - Live bookmark fails to load if network connection is available *after* firefox launch
: Live bookmark fails to load if network connection is available *after* firefo...
Product: Firefox
Classification: Client Software
Component: Bookmarks & History (show other bugs)
: 4.0 Branch
: x86 Windows 7
: -- normal (vote)
: ---
Assigned To: Nobody; OK to take it and work on it
: Marco Bonardo [::mak]
Depends on: 663104
  Show dependency treegraph
Reported: 2011-04-01 20:17 PDT by Raj
Modified: 2011-06-21 02:30 PDT (History)
2 users (show)
See Also:
Crash Signature:
QA Whiteboard:
Iteration: ---
Points: ---
Has Regression Range: ---
Has STR: ---


Description Raj 2011-04-01 20:17:34 PDT
User-Agent:       Mozilla/5.0 (Windows NT 6.1; rv:2.0) Gecko/20100101 Firefox/4.0
Build Identifier: Mozilla/5.0 (Windows NT 6.1; rv:2.0) Gecko/20100101 Firefox/4.0

If firefox is launched when no network connection is available, and later if I connect to a network, Live bookmarks fail to load until firefox is restarted

Reproducible: Always

Steps to Reproduce:
1. Ensure no network connections are available
2. Launch firefox
3. Connect to a network
4. Check your live bookmarks
Actual Results:  
In the drop down, you would see 'Live bookmark feed failed to load'. Try to refresh. Still it shows the same error

Expected Results:  
Live book mark refresh should happen successfully

Comment 1 Raj 2011-04-01 20:19:18 PDT
Forgot to mention one point. Normal browsing happens fine. No problems there. It's just that Live bookmarks do not refresh. If i click on existing stale entries of the live feed, it connects fine.
Comment 2 (mostly gone) XtC4UaLL [:xtc4uall] 2011-04-02 05:33:51 PDT
Bug 410101 related?
Comment 3 Marco Bonardo [::mak] 2011-06-21 02:30:42 PDT
I suspect here the problem is not that the feed fail to load, but that we were not removing the "Live bookmark feed failed to load" message correctly.
bug 663104 should have taken care of that.

Note You need to log in before you can comment on or make changes to this bug.