This site will have limited functionality while we undergo maintenance to improve your experience. If an article doesn't solve your issue and you want to ask a question, we have our support community waiting to help you at @FirefoxSupport on Twitter and/r/firefox on Reddit.

Search Support

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

Learn More

Hierdie gesprek is in die argief. Vra asseblief 'n nuwe vraag as jy hulp nodig het.

Ancestry results using Firefox are not handled correctly

  • 2 antwoorde
  • 3 hierdie probleem
  • 6 views
  • Laaste antwoord deur Essdeebee

more options

Latest version of Firefox (for PC) does not handle search results from Ancestry properly. It should remember whether I want results ordered by Category or Result, but doesn't. It always defaults to Category. It should also remember that I want 50 results per page, but always defaults to 20. If I change it to 50, it reverts the order back from Record to Category. If I ask for the 2nd page of results (ie records 21 to 40), I just get the first page again. This is NOT an Ancestry problem - it works fine on IE (as it used to on Firefox). Ancestry research on Firefox is fast becoming impossible. Until it is fixed, I will have to use IE or Chrome for my Ancestry research.

Latest version of Firefox (for PC) does not handle search results from Ancestry properly. It should remember whether I want results ordered by Category or Result, but doesn't. It always defaults to Category. It should also remember that I want 50 results per page, but always defaults to 20. If I change it to 50, it reverts the order back from Record to Category. If I ask for the 2nd page of results (ie records 21 to 40), I just get the first page again. This is NOT an Ancestry problem - it works fine on IE (as it used to on Firefox). Ancestry research on Firefox is fast becoming impossible. Until it is fixed, I will have to use IE or Chrome for my Ancestry research.

Gekose oplossing

Web sites use cookies to store user options on the users computer.

Many site issues can be caused by corrupt cookies or cache.

  • Clear the Cache and
  • Remove Cookies Warning ! ! This will log you out of sites you're logged in to.

Type about:preferences<Enter> in the address bar.

  • Cookies; Select Privacy. Under History, select Firefox will Use Custom Settings. Press the button on the right side called Show Cookies. Use the search bar to look for the site. Note; There may be more than one entry. Remove All of them.
  • Cache; Select Advanced > Network. Across from Cached Web Content, Press Clear Now.

If there is still a problem, Start Firefox in Safe Mode {web link} While you are in safe mode;

Type about:preferences#advanced<Enter> in the address bar.

Under Advanced, Select General. Look for and turn off Use Hardware Acceleration.

Poke around safe web sites. Are there any problems?

Then restart.

Lees dié antwoord in konteks 👍 2

All Replies (2)

more options

Gekose oplossing

Web sites use cookies to store user options on the users computer.

Many site issues can be caused by corrupt cookies or cache.

  • Clear the Cache and
  • Remove Cookies Warning ! ! This will log you out of sites you're logged in to.

Type about:preferences<Enter> in the address bar.

  • Cookies; Select Privacy. Under History, select Firefox will Use Custom Settings. Press the button on the right side called Show Cookies. Use the search bar to look for the site. Note; There may be more than one entry. Remove All of them.
  • Cache; Select Advanced > Network. Across from Cached Web Content, Press Clear Now.

If there is still a problem, Start Firefox in Safe Mode {web link} While you are in safe mode;

Type about:preferences#advanced<Enter> in the address bar.

Under Advanced, Select General. Look for and turn off Use Hardware Acceleration.

Poke around safe web sites. Are there any problems?

Then restart.

more options

Many thanks Fred. Not being a techie, it took me a couple of minutes to find out how to find the Cache bit, but I got there. It seems to have worked.