InformAction Forums

I have seen when I create a new tab it's not whitelisted. It's blocked.
So sometimes when I create a new tab it's bugging. So I need to make it whitelisted.

Everything else is whitelisted from the beginning, So why not about:newtab?

munkdunk wrote:I have seen when I create a new tab it's not whitelisted. It's blocked.
So sometimes when I create a new tab it's bugging. So I need to make it whitelisted.

Everything else is whitelisted from the beginning, So why not about:newtab?

If you simply create a new tab with a blank URL, there is nothing to whitelist, because there is nothing trying to load.
Only after you enter an address are requests made. Then they will show in the menu.

If you are referring to opening a link in a new tab, the new tab should apply whatever permissions you have already given to the linked site:
Whitelisted, Untrusted, or, if none of those, they go into the normal "default-deny" zone, blocking all by default for your safety.
Then you use the menu to allow or temp-allow as you choose.

Is this not the case for you? If not, please provide exact steps to reproduce:
1) Page you are on
2) Link you are opening in new tab
3) Existing permissions, if any, for the new tab's site.

Also, if you are using "Allow sites opened through bookmarks" on NS Options > General tab, those should work regardless of whether tab or window.

Hi, I'm also experiencing this. For me it's because I'm opening a bookmarklet on the new tab. Here's the bookmarklet: I've given it the keyword 'crs' so I can type in "crs biol 343" in the address bar and it takes me to the desired page. It used to work from new tabs but doesn't anymore -- unfortunately, I don't know if it was after an update to Firefox or NoScript.

I thought it might be related to recent Firefox's about:newtab pages so I disabled it in about:config with "browser.newtabpage.enabled=false" but it didn't help.

Any ideas?

Thanks,
Rik

Rik,

Did you not get the error message that I did when trying to load your bookmarklet? (Fx 15.0.1, NS 2.5.5rc2 = 2.5.5, Win XP)

javascript: and data: URIs typed or pasted in the address bar are disabled to prevent social engineering attacks.
Developers can enable them for testing purposes by toggling the "noscript.allowURLBarJS" preference.

The OP didn't mention bookmarklets, but I think we have *your* answer.
Please consider the risks that caused Giorgio to add this block, before toggling the preference.

crs biol 343 works for me in a new tab, loading a URL like, http://www.calendar.ubc.ca/?code=biol#343.

Now in a new window, if I am quick in pasting it in, then I get nothing - initially.
If I wait a moment, then it works in the new window too.
(javascript: / data: URI being bypassed)

Typing the javascript: code directly into the addressbar would (should) bring up the warning.
If opened from a bookmark (keyword) it does not. (Expected behavior.)

See if you don't have something else interfering?

Oh, & most importantly, if you don't have NoScript 2.5.5, you'll need at least that, otherwise you're running into a Mozilla bug that is affecting you.

OK, confirmed-ish.
The keyword does not work within the context of about:newtab.
It does work with about:blank.

(SeaMonkey does not have about:newtab so I did not see it initially.)

And rikblok's part of this thread is invalid, because it looks like JavaScript does not work within the context of about:newtab at all - regardless of extensions.

Bug 728313 - Bookmarklet fails on about:newtab