[Resolved] New Google Search interface breaks down

[jerriy]

I'm still not sure whether noscript or another addon is causing it but I'm having trouble with on-and-off blockade of the dropdown/submenu of the new ugly and horrible google menu system that is now situated on top of the search results page (used to be a sidebar feature). This second row of google search options is supposed to drop down below the first row when you hit the "search tools" menu button on the first row - but now it is not appearing at all, or it flickers and disappears.

[Giorgio Maone]

It should have already been fixed by 2.6.2. Please confirm.

[jerriy]

Acknowledged.
Thank you!

PS: Since I'm here I might as well quickly ask something else:
I have an issue with noscript blocking something at Google picasa (the online version). The issue is when I go to picasaweb.google.com and click on "my photos" tab >> then open any album >> then click on "Add photos" menu option, I get a NS message that something has been blocked and I am seemingly redirected to a blank picasaweb page with a message:

Goodbye attachments. Hello Google Drive.
With Google Drive, you never have to send another email attachment again. Just share a link to any file you store in Google Drive. That way everyone has access to the same file, same version - automatically

And NoScript's message is that it has filtered a potential cross-site scripting (XSS) attempt...

The problem seems to be that the website picasaweb.google.com and at least one other google place (plus.google.com) are interconnected and that is causing the noscript block.

Anyway since I don't know whether this is related something new in google or something I tweaked in my NS setting or not (or perhaps other add-ons) I decided to solve this issue by simply creating a new exception at your anti-XSS protection exception list:

Code: Select all

^https://([a-z]*)\.google\.com/*

That solved the issue. But the question is, is that a good thing? I feel like I white-listed anything and everything related to "google" (that was not my intention). What is the better way to just solve the picasaweb "add images" issue?

This is how my total list looks like:

Code: Select all

^https?://([a-z]+)\.google\.(?:[a-z]{1,3}\.)?[a-z]+/(?:search|custom|\1)\?
^https?://([a-z]*)\.?search\.yahoo\.com/search(?:\?|/\1\b)
^https?://[a-z]+\.wikipedia\.org/wiki/[^"<>\?%]+$
^https?://translate\.google\.com/translate_t[^"'<>\?%]+$
^https://secure\.wikimedia\.org/wikipedia/[a-z]+/wiki/[^"<>\?%]+$
^https?://[a-z\-]+\.wikipedia\.org/w/index\.php
^https?://commons\.wikimedia\.org/w/index\.php
^https://([a-z]*)\.google\.com/*

[Giorgio Maone]

Could you please post any [NoScript XSS] message you get in your Error Console (Ctrl+Shift+J) when this happens?

[jerriy]

When I click the "add photos" (after removing my self created exception) the noscript blocked script message appears and then the following item comes in the the "Errors" tab of the error console:

Code: Select all

Timestamp: 26/11/2012 15:34:06
Error: TelemetryStopwatch: key "FX_SESSION_RESTORE_COLLECT_DATA_MS" was already initialized
Source File: resource://gre/modules/TelemetryStopwatch.jsm
Line: 53

[therube]

Bug 732874 - Telemetry stopwatch: "key was already initialized" errors in logs, but that should have nothing to do with NoScript.

You want to post messages that show: [NoScript XSS]

[jerriy]

^ I know (because I get the same above error message even when I add or keep my self created "google exception"

But that is the only "Error" message I get. Other than that I only get "warnings"

[jerriy]

By the way I might add the problem only happened in the last two or three weeks (before that I had no problem adding photos to my picasaweb album via this method)

[Giorgio Maone]

^ I know (because I get the same above error message even when I add or keep my self created "google exception"

But that is the only "Error" message I get. Other than that I only get "warnings"

In facts, [NoScript XSS] lines should not be in the "Error" section, neither in the "Warnings" one, but in the "Messages" (blue) section.

[jerriy]

Oh, ok, I thought there is nothing there but I noticed that IS indeed a noscript "message" there but guess what, I can't copy it!

This console message (actually two of them) appear and then disappear instantly!

[jerriy]

I loaded the blocked script in order to copy the message from the NS warning pop up

Code: Select all

UNSAFELY reloading a suspicious

GET [https://docs.google.com/picker?protocol=gadgets&relayUrl=https://picasaweb.google.com/s/v/lighthousefe_101.04/rpc_relay.html&hostId=pwa&hl=en_US&rpcService=lhid_picker&rpctoken=1g2w3qxma5hat&selectButtonLabel=Ok&title&navHidden=true&multiselectEnabled=true&white=true&chromeMode=none&uploadToAlbumId=5765550811582142049&nav=((%22upload%22,null,%7B%22query%22:%22photos%22,%22data%22:%7B%22owner_name%22:%22111200871816508377​435%22,%22disable_asbe_notif​ication%22:%22false%22,%22streamid%22:null%7D%7D))]

FROM [https://picasaweb.google.com/lh/webUpload?uname=11120087181650837743​5&aid=5765550811582142049&continue=https%3A%2F%2Fpicasaweb.google.com%2F111200871816508377​435%2FW8]

[jerriy]

Finally! Here it is (thank God for screen capture)

[Giorgio Maone]

Fixed in latest development build 2.6.3rc3, please check, thanks.

[jerriy]

^ Fantastic!
Thanks!
Bye!