NoScript menu changes between Firefox 16 and 17

[mjh563]

Hi, I don't know if this is a bug or not, but there's a difference in the domains displayed in the NoScript menu in Firefox 17 compared with Firefox 16.

Steps to reproduce:

1. Load NoScript into a clean profile in Firefox 16
2. Go to http://community.ebay.co.uk
3. Click on 'Forbid googleapis.com' (it's initially allowed due to being in the default whitelist)
4. The menu option changes to 'Allow googleapis.com'

Now repeat the STR using Firefox 17.
The difference is that in Step 4 the menu option changes to 'Allow ajax.googleapis.com'

This image shows the difference
http://i50.tinypic.com/2hnccnn.png

[Giorgio Maone]

Investigating, thanks.

[FRANK712]

The difference is that in Step 4 the menu option changes to 'Allow ajax.googleapis.com'

Confirmed even in the "old" FX12.

[Giorgio Maone]

Ooops, I was sure I had posted the answer here, but actually just tweeted about it.

[therube]

Could you say that in Italian cause I sure don't understand "tweets" (or whatever they're called).

[Giorgio Maone]

googleapis.com, googlecode.com, blogspot.com and a bunch of other similar sites where subdomains are in potentially "owned" by different authorities are now treated like "co.uk" & C.

[therube]

OK, then why are we now (>16) seeing the ajax, ajax.googleapis.com?

Oh, so that's what it means.
googleapis.com is being treated as a TLD, so when we display 2nd level Domains, we get ajax .

Thanks.

So in addition to ajax we can have things like fonts & youtube & ...

[Thrawn]

Interesting. If googleapis.com is now treated as a TLD, then should the default whitelist change to be more specific?

I configure NoScript to use full addresses anyway .