搜索 | 用户支持

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

详细了解

Lowes website will not go past page 1- page 2 "whited out"

  • 3 个回答
  • 1 人有此问题
  • 18 次查看
  • 最后回复者为 bobo22

more options

Since updated to FF29 I can not get past page 1 when searching Lowes.com. Page 2 is "whited out". I can use IE on same website and everything works, so problem would appear to be with Firefox.

Since updated to FF29 I can not get past page 1 when searching Lowes.com. Page 2 is "whited out". I can use IE on same website and everything works, so problem would appear to be with Firefox.

被采纳的解决方案

Start Firefox in Safe Mode to check if one of the extensions (Firefox/Tools > Add-ons > Extensions) or if hardware acceleration is causing the problem.

  • Switch to the DEFAULT theme: Firefox/Tools > Add-ons > Appearance
  • Do NOT click the Reset button on the Safe Mode start window
定位到答案原位置 👍 0

所有回复 (3)

more options

You can try these steps in case of issues with web pages:

You can reload web page(s) and bypass the cache to refresh possibly outdated or corrupted files.

  • Hold down the Shift key and left-click the Reload button
  • Press "Ctrl + F5" or press "Ctrl + Shift + R" (Windows,Linux)
  • Press "Command + Shift + R" (Mac)

Clear the cache and cookies only from websites that cause problems.

"Clear the Cache":

  • The image "new fx menu" does not exist. > Options/Preferences> Advanced > Network > Cached Web Content: "Clear Now"

"Remove Cookies" from sites causing problems:

  • The image "new fx menu" does not exist. > Options/Preferences > Privacy > "Use custom settings for history" > Cookies: "Show Cookies"
more options

选择的解决方案

Start Firefox in Safe Mode to check if one of the extensions (Firefox/Tools > Add-ons > Extensions) or if hardware acceleration is causing the problem.

  • Switch to the DEFAULT theme: Firefox/Tools > Add-ons > Appearance
  • Do NOT click the Reset button on the Safe Mode start window
more options

Moses, I tried your suggestions, but did not fix problem. I did however try Cor-el 's suggestion and found that HTTPS-Everywhere 3.5.1 was the apparent culprit.