Join the AMA (Ask Me Anything) with the Firefox leadership team to celebrate Firefox 20th anniversary and discuss Firefox’s future on Mozilla Connect. Mark your calendar on Thursday, November 14, 18:00 - 20:00 UTC!

Шукати в статтях підтримки

Остерігайтеся нападів зловмисників. Mozilla ніколи не просить вас зателефонувати, надіслати номер телефону у повідомленні або поділитися з кимось особистими даними. Будь ласка, повідомте про підозрілі дії за допомогою меню “Повідомити про зловживання”

Докладніше

Ця тема перенесена в архів. Якщо вам потрібна допомога, запитайте.

Chrome but not Firefox proper loads images in ancestry.com and MyHeritage.com

  • 1 відповідь
  • 1 має цю проблему
  • 1 перегляд
  • Остання відповідь від cor-el

more options

Example for ancestry.com which changed from being properly accessible on Firefox to the unusable mess below but are still correctly loading in Chrome. Have even talked to ancestry.com support and they say it is a Firefox problem. Your help would be very much appreciated. Cookies and cached have been addressed and do not appear to be the problem. It has been months since ancestry.com loaded properly and only in the last week has MyHeritage.com become the same problem after having always loaded properly. Example for ancestry.com:

Skip Ancestry main menu Main Menu Ancestry Home

    Home
    Trees
    Search
    DNA
    Help
    Extras
    Cart 1
    Hints
    Messages
    JerryWeaver44

Home

Family Trees

    Start a New Tree
    Upload a GEDCOM
Example for ancestry.com which changed from being properly accessible on Firefox to the unusable mess below but are still correctly loading in Chrome. Have even talked to ancestry.com support and they say it is a Firefox problem. Your help would be very much appreciated. Cookies and cached have been addressed and do not appear to be the problem. It has been months since ancestry.com loaded properly and only in the last week has MyHeritage.com become the same problem after having always loaded properly. Example for ancestry.com: Skip Ancestry main menu Main Menu Ancestry Home Home Trees Search DNA Help Extras Cart 1 Hints Messages JerryWeaver44 Home Family Trees Start a New Tree Upload a GEDCOM
Прикріплені знімки екрана

Обране рішення

This happens when CSS files are blocked.

If you use extensions ("3-bar" menu button or Tools -> Add-ons -> Extensions) that can block (wanted) content (Adblock Plus, NoScript, Disconnect, Ghostery, Privacy Badger, uBlock Origin) always make sure such extensions do not block (wanted) content.

Firefox shows the shield icon at the left end of the location/address bar in case Content Blocking is blocking content.

  • click the shield icon for more detail and possibly disable the protection

You can check the Web Console about what content is blocked


You can check the Web Console (Tools -> Web Developer) for messages about blocked content and about the presence of mixed or unsafe content.

You can check the Network Monitor to see if content is blocked or otherwise fails to load.

If necessary use "Ctrl+F5" or "Ctrl+Shift+R" (Mac: Command+Shift+R) to reload the page and bypass the cache to generate a fresh log.

Читати цю відповідь у контексті 👍 0

Усі відповіді (1)

more options

Вибране рішення

This happens when CSS files are blocked.

If you use extensions ("3-bar" menu button or Tools -> Add-ons -> Extensions) that can block (wanted) content (Adblock Plus, NoScript, Disconnect, Ghostery, Privacy Badger, uBlock Origin) always make sure such extensions do not block (wanted) content.

Firefox shows the shield icon at the left end of the location/address bar in case Content Blocking is blocking content.

  • click the shield icon for more detail and possibly disable the protection

You can check the Web Console about what content is blocked


You can check the Web Console (Tools -> Web Developer) for messages about blocked content and about the presence of mixed or unsafe content.

You can check the Network Monitor to see if content is blocked or otherwise fails to load.

If necessary use "Ctrl+F5" or "Ctrl+Shift+R" (Mac: Command+Shift+R) to reload the page and bypass the cache to generate a fresh log.