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.

ค้นหาฝ่ายสนับสนุน

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.

เรียนรู้เพิ่มเติม

about:blank not rendering

  • 2 การตอบกลับ
  • 1 คนมีปัญหานี้
  • 2 ครั้งที่ดู
  • ตอบกลับล่าสุดโดย mifinti

more options

As far as I can tell, Firefox is not rendering about:blank under certain conditions.

I am using "chrome\userContent.css" to customize about:blank, but sometimes Firefox is producing a blank white screen instead.

When opening a new window and sometimes when a new tab is created by closing the last one in a window, this style is not applied. "Tools > Page Info" confirms that the unstyled page is indeed about:blank. Also opening the developer tools to the "Style Editor" or viewing the page source will fix the issue.

As far as I can tell, Firefox is not rendering about:blank under certain conditions. I am using "chrome\userContent.css" to customize about:blank, but sometimes Firefox is producing a blank white screen instead. When opening a new window and sometimes when a new tab is created by closing the last one in a window, this style is not applied. "Tools > Page Info" confirms that the unstyled page is indeed about:blank. Also opening the developer tools to the "Style Editor" or viewing the page source will fix the issue.

การตอบกลับทั้งหมด (2)

more options

Some additional weirdness, if I point the homepage at an HTML file that contains a <meta http-equiv="refresh" content="0;url=about:blank">. It exhibits the same issue; sometimes about:blank renders without respect to the userContent.css. However if I change that to refresh after 1 second delay, the always renders correctly.

more options

This appears to be a known bug (#1422507) since v57.