Rechercher dans l’assistance

Évitez les escroqueries à l’assistance. Nous ne vous demanderons jamais d’appeler ou d’envoyer un SMS à un numéro de téléphone ou de partager des informations personnelles. Veuillez signaler toute activité suspecte en utilisant l’option « Signaler un abus ».

En savoir plus

RSS Live Bookmarks doesn't update site icons any more

  • 7 réponses
  • 23 ont ce problème
  • 1 vue
  • Dernière réponse par TsarNikky

more options

Before this update, RSS Live Bookmarks used to update the links with the site icon (if any) whenever I visited it, much like it does with regular bookmarks. Checking for new feeds was easy this way.

But ever since the new version (and I've noticed it on the Nightly version for some time now), I only have some generic icons which are either light grey (not visited) or dark grey (visited) with Nasa Launch theme. With default theme, it's just a yellow icon and a grey one. It's a lot harder to spot which I've read and which I haven't. Also, since the update, expanding the feed is MUCH slower. Even in smaller feeds, like APOD, but especially on large ones, like Order of the Stick.

Is there any way to revert this?

Before this update, RSS Live Bookmarks used to update the links with the site icon (if any) whenever I visited it, much like it does with regular bookmarks. Checking for new feeds was easy this way. But ever since the new version (and I've noticed it on the Nightly version for some time now), I only have some generic icons which are either light grey (not visited) or dark grey (visited) with Nasa Launch theme. With default theme, it's just a yellow icon and a grey one. It's a lot harder to spot which I've read and which I haven't. Also, since the update, expanding the feed is MUCH slower. Even in smaller feeds, like APOD, but especially on large ones, like Order of the Stick. Is there any way to revert this?

Solution choisie

This is the kind of Mozilla behavior that irritates and angers users. Whatever improvements that are supposed to come with the update are largely negated when things that used to work no longer work. Now, users have to hunt around to find a fix. Not nice.

Lire cette réponse dans son contexte 👍 6

Toutes les réponses (7)

more options

in firefox 13 the handling of live bookmarks has changed quite substantially, so the missing favicons are a by-product of that, but an expected behaviour unfortunately. http://ilias.ca/blog/2012/06/live-bookmarks-now-indicate-which-items-are-unread/

the feeds are now also only loaded on demand and not constantly updated in the background for performance purposes. this might also explain why the feed is taking longer to load when you open it the first time in a session.

Modifié le par philipp

more options

Ok, I understand the slow loading bit and the change behind it. I can even say that I agree with it. But is there no way to get back the site icons (or favicons)? I always knew which ones I had read because the other ones would have just a generic icon. If there was a favicon on a feed, I had read it already. Now it's much harder to see the difference, especially with certain skins.

more options

if the icons don't work well in the theme you're using, you could try to contact the developers of the theme. like the rest of the userinterface those rss icons are fully customizable.

maybe there will also an extension one day that will bring back the old favicons of a site. sorry if i cannot offer a better solution at the moment...

more options

Thanks for your help.

more options

...the feeds are now also only loaded on demand and not constantly updated in the background for performance purposes....

can i change that somehow??

and, btw, who creates the releasenotes?? neither http://www.mozilla.org/en-US/firefox/13.0/releasenotes/ nor http://www.mozilla.org/en-US/firefox/13.0.1/releasenotes/ mention that. And also the "complete list of changes" on http://www.mozilla.org/en-US/firefox/13.0/releasenotes/buglist.html do not mention that.

more options

@yehoudin, unfortunately there is no setting to change that, since it was quite a fundamental change.

there are quite a few related entries in the full bug list for that (#432097, #453530) - however the main tracking bug (#613588) for the change isn't listed in there & i don't know the reason for that...

more options

Solution choisie

This is the kind of Mozilla behavior that irritates and angers users. Whatever improvements that are supposed to come with the update are largely negated when things that used to work no longer work. Now, users have to hunt around to find a fix. Not nice.