Closed Bug 278247 Opened 19 years ago Closed 6 years ago

Clicking on "Live bookmark feed failed to load" should perform refresh


(Firefox :: Bookmarks & History, enhancement)

Not set





(Reporter: R.Kelley.Cook, Unassigned)


(Blocks 1 open bug)


(Keywords: polish, Whiteboard: [Advo])

When one gets a "Live bookmark feed failed to load" from say not yet authorizing
with the proxy server (See bug 266348).  Clicking on that "Failed to load" line
should automatically attempt a refresh.

Otherwise you need to right click on that same Live Bookmark and choose "Refresh".

This awkwardness is compounded on systems like the Mac which don't have right
mouse buttons.

Severity: normal → enhancement
Ever confirmed: true
OS: Windows XP → All
Version: 1.0 Branch → unspecified
Assignee: vladimir+bm → nobody
We should try to get this for Firefox 2. Adding to the UI polish list.
Keywords: polish
Target Milestone: --- → Firefox 2 beta1
cc: mconnor, gavin, for ideas of who might be able to handle it; this sounds like a pretty easy patch to my uninformed mind (adding a command reference and event listener to the item?) so it might be a good firstbug if you have a candidate.

We should also change the content to be:

  "Feed not found. Click to reload Live Bookmark"

or even just

  "Click to load Live Bookmark"
sorry for bugspam, long-overdue mass reassign of ancient QA contact bugs, filter on "beltznerLovesGoats" to get rid of this mass change
QA Contact: mconnor → bookmarks
The first time i see a "Live Bookmark faild to load" i instantly clicked on it, thinking to a reload... This should be definetely be corrected for Firefox 3, it's  useless to know that the feed failed if i cannot try to reload it (the right click menu option is too much hidden, and difficult to find). 
Component: Bookmarks → Places
QA Contact: bookmarks → places
Assignee: nobody → swon
Target Milestone: Firefox 2 beta1 → Firefox 3 beta1
Is there a specific site I can test this on?
this happens with connection hangs/blocks or when a website is overloaded or when there are permission problems, so no easy site to reproduce. I think that it happens when the connection hangs while downloading the xml file (or if "something" does not let download the xml after the request has been done). 
See bug 333416 for a similar problem, the nsLivemarkService tries to load about:livemark-failed but that address does not exists.

i have attached a possible temporary workaround for both problems in Bug 333416
Assignee: swon → nobody
Target Milestone: Firefox 3 M7 → Firefox 3 M8
Target Milestone: Firefox 3 M8 → Firefox 3 M9
Target Milestone: Firefox 3 M9 → Firefox 3 M10
Depends on: 407468
I never had this message with Firefox 2.
I'm bitten by this very often with Firefox 3.0b1.
I don't use any proxy.
I'm on a laptop, which I'm hibernating when moving from place to place.
I happens with many differents rss feeds (slashdot,...)
When this happen, the problem will only disappear if I restart Firefox.
I don't understand how this bug can happen.
If Firefox succeeds to connect to see that one feed is updated then surely there's enough network connectivity so it should work to download the titles ?
Has the code fetching the title regressed between firefox 2 and 3 ?
Target Milestone: Firefox 3 M10 → Firefox 3 M11
Target Milestone: Firefox 3 beta3 → ---
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.

Component: Places → Bookmarks & History
QA Contact: places → bookmarks
Blocks: cuts-control
Hardware: x86 → All
Whiteboard: [Advo]
Per policy at If this bug is not an enhancement request or a bug not present in a supported release of Firefox, then it may be reopened.
Closed: 6 years ago
Resolution: --- → INACTIVE
You need to log in before you can comment on or make changes to this bug.