We're calling on all EU-based Mozillians with iOS or iPadOS devices to help us monitor Apple’s new browser choice screens. Join the effort to hold Big Tech to account!

搜索 | 用户支持

防范以用户支持为名的诈骗。我们绝对不会要求您拨打电话或发送短信,及提供任何个人信息。请使用“举报滥用”选项报告涉及违规的行为。

详细了解

photos in news items, et al, abend; IE works just fine

  • 2 个回答
  • 1 人有此问题
  • 1 次查看
  • 最后回复者为 garyk9

more options

Looking at News items (or other still pics) in Roadrunner, still photos abend, showing a blank, white screen with only the photo's caption across the top of the screen, left to right. IE works just fine. This has happened since I downloaded Firefox 12. News reports with action films seem to work fine - only the stills abort.

Looking at News items (or other still pics) in Roadrunner, still photos abend, showing a blank, white screen with only the photo's caption across the top of the screen, left to right. IE works just fine. This has happened since I downloaded Firefox 12. News reports with action films seem to work fine - only the stills abort.

所有回复 (2)

more options

If images are missing then check that you aren't blocking images from some domains.

  • Check the permissions for the domain in the current tab in "Tools > Page Info > Permissions"
  • Check that images are enabled: Tools > Options > Content: [X] Load images automatically
  • Check the exceptions in "Tools > Options > Content: Load Images > Exceptions"
  • Check the "Tools > Page Info > Media" tab for blocked images (scroll through all the images with the cursor Down key).

If an image in the list is grayed and there is a check-mark in the box "Block Images from..." then remove that mark to unblock the images from that domain.

Make sure that you do not block third-party images, the permissions.default.images pref should be 1.

There are also extensions (Tools > Add-ons > Extensions) and security software (firewall, anti-virus) that can block images.

more options

The problem turned out to be with the 'Search.com' bar ('Search.com 1.0.0.0'). All was well when I disabled it, but the problem re-appeared when re-enabled. Needless to say, it is disabled now.

May I be so bold as to suggest that there may be an incompatibility issue here? I did not have a problem of this sort with earlier versions of Firefox - only V12. I'd like to know your thoughts, please.

I did look at all of your other suggestions, too - thoroughly. Everything else checked-out as they should have.

Unless you or someone else has something to add or ask, insofar as I am concerned this issue is resolved. With much thanks for your kind attention.

garyk9 Sch'dy, NY