InformAction Forums

NoScript Interferes with Home Button when set to about:blank

Set your home page to about:blank
Visit https://www.yahoo.com
Hit your Home button

Note that a bunch of icons clear from the URLbar; 3 little dots, some sort of down arrow thing, & a star.

Oh, isn't that interesting.
What I think is happening is the page does "load" about:blank, but it just doesn't "blank out".

Anyhow, if you hit the Home button a second (maybe a third) time, the page does show blank.


Don't know if about:blank is in NoScript's whitelist ? or even how to determine if it is or is not ? or how to add it if I wanted to?


FF 60
NoScript 10
(credit to Grumpus. & mightyglydd for mentioning NoScript)



Mozillazine thread, Double and triple clicks to clear window (Linux) Not yet..

Sigh, why is FF 60 breakin so many things with NS...

Anyhow, not a NS bug. Apparently having content CSS matching about:blank and running at document_start is what breaks the page refreshing when navigating to about:blank. The CSS file doesn't even need to have anything in it!

skriptimaahinen wrote:... having content CSS matching about:blank and running at document_start ...

Can you explain in more detail what that means? Is this a reported Firefox bug? Is there a workaround?

why is FF ... breakin so many things

Because it is not evolving it is changing.
With all kinds of (relatively) untold changes between versions, additions, deletions, ..., that an extension author essentially has to have a corresponding extension version for every different FF version (not to mention actually physically making the changes to account for the changes made in FF itself).

IOW, it's a no-win situation. You hope for stability, but you'll never know if you have it.

@David_L: Unfortunately it's a internal webextension thing - nothing that end user can do about. Giorgio could make a workaround, but the problem is quite benign and simply refreshing clears it, so it likely doesn't warrant one. Better just wait for a FF fix. Can't find related report on Bugzilla though. Gues I might need to make one.

@therube: Aren't you on a positive mood today?

Heh, yeah. Every so often it's good to throw out a little rant to keep things entertaining .

Resolved, https://forums.informaction.com/viewtop ... 066#p97066.

Thank you.

A little bump...

While NoScript implemented a work-around to account for this,
FF 61 now offers (after a long absence) a setting for "Home page and new windows" (& "New tabs") of -> "Blank Page".

And while "Blank Page" does in fact give you a blank page (hurray!), a setting of "Blank Page" I'll assume is not checked for in NoScript's work-around, & as the underlying bug is not fixed, so using FF's new "Blank Page" setting causes the issue to manifest itself, again.

A work-around to the work-around to the bug, would be to select a "Custom URLs..." & set it to about:blank (rather then "Blank Page").

It happens again? The workaround should be still OK, as we don't really "select" the blank page in any way, we just stopped doing what was causing the bug. But if it's happening again, that means there is a new trigger for the bug. Cannot test myself as the newest FF has not yet landed on the Ubuntu repos, but will report back as soon as it does.

I could have sworn I saw this.
But after your post, I went back & looked again & was unable to duplicate.
I'll keep looking...