Can't allow sites for adding extensions

Bug #89071 reported by Patrice Vetsel
6
Affects Status Importance Assigned to Milestone
Mozilla Firefox
Invalid
Medium
firefox (Ubuntu)
Won't Fix
Undecided
Unassigned
firefox-3.0 (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

Binary package hint: firefox

When i go to http://www.google.com/tools/firefox/ an try to install an extension, the top yellow bar appear but clicking on "modification of options" don't do anything.

version 2.0.0.2+1-0ubuntu1

Tags: mt-confirm
Changed in firefox:
importance: Undecided → High
Revision history for this message
Freddy Martinez (freddymartinez9) wrote :

Can *not* reproduce on my 2.0.0.2 Feisty Herd 5 system. Does this occur under a new profile. Try launching 'firefox -profilemanager' in a terminal (no quotes) and creating a new profile.

Changed in firefox:
assignee: nobody → freddymartinez9
status: Unconfirmed → Needs Info
Revision history for this message
Patrice Vetsel (vetsel-patrice) wrote :

Have you tried the link proposed ?

It's seems that this is specifically this link that's not working. I'v tried other sites offering extensions and firefox worked as expected.
I'v desinstalled totem-mozilla/flash, created new user, deleted and created new one. Nothing change this problem.

Revision history for this message
In , Rene Rattur (renerattur) wrote :

User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.1.2) Gecko/20070219 Firefox/2.0.0.2
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.1.2) Gecko/20070219 Firefox/2.0.0.2

When trying to install Google Weblogger Comments extension firefox prevents it by displaying a bar on the top of the browser window. When clicking on the Edit Options button on the bar, nothing happens.

Reproducible: Always

Steps to Reproduce:
1. Go to http://tools.google.com/firefox/webcomments/install.html
2. Click Agree and Install button.
3. Click the Edit Options button.

Actual Results:
Nothing happens.

Expected Results:
Popped up a configuration window to allow certain sites to install code.

Revision history for this message
In , Jmjeffery (jmjeffery) wrote :

Functionality has been removed. Use this extension:
https://addons.mozilla.org/firefox/2821/

Revision history for this message
In , Jmjeffery (jmjeffery) wrote :

(In reply to comment #1)
> Functionality has been removed. Use this extension:
> https://addons.mozilla.org/firefox/2821/
>

Ack, nm, posted to wrong bug.
>

Revision history for this message
In , Robert-bugzilla (robert-bugzilla) wrote :

Appears to be a regression from bug 359012.

JSConsole output
Error: webNav.currentURI has no properties
Source File: chrome://browser/content/browser.js
Line: 580

Revision history for this message
In , Enn (enndeakin) wrote :

Works fine for me. I click the button and get the Install dialog. If I remove
addons.mozilla.org from the whitelist, I get the notification and can click the
button to edit the options.

Revision history for this message
In , Robert-bugzilla (robert-bugzilla) wrote :

For myself using the official 2.0.0.2 I get the error as stated in comment #3 with and without removing addons.mozilla.org from the whitelist using a new profile as well as with my regular profile.

Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.1.2) Gecko/20070219 Firefox/2.0.0.2

Revision history for this message
In , Robert-bugzilla (robert-bugzilla) wrote :

Neil, what OS did you test this on? Perhaps this is Windows only.

Revision history for this message
In , Philringnalda (philringnalda) wrote :

Trunk Mac, I get the browsermessage with the broken button; 2.0.0.2 Win, I get the install prompt with amo whitelisted, or a working browsermessage that whitelists amo (mmm, confusing, since their instructions say to whitelist tools.google.com).

Or, possibly it's a race condition, and that should be "dialup, I get the browsermessage with the broken button, decent connection things work (other than GOOG's insistence on confusing hell out of the minority to save the majority a single click)." I can check various other builds and operating systems when I get back to a slow connection later to see if that makes a difference.

Revision history for this message
In , Robert-bugzilla (robert-bugzilla) wrote :

Edit Options works after backing out the patch in bug 359012 though it auto-fills with tools.google.com.

Revision history for this message
In , Mike Connor (mconnor) wrote :

This seems to work for most users, until we have a clear view on what's causing the failure here in some cases not going to block.

Should fix this for 1.8.1.4 though.

Revision history for this message
John Vivirito (gnomefreak) wrote :

That seems to not be a firefox bug. If you use the mozilla.com site for addons do they work? Do they have the same ones that are on the link you gave? Please try looking for the ones you wanted from http://www.google.com/tools/firefox/. Look for them at: https://addons.mozilla.org/firefox/ and let us know if they work.

Revision history for this message
Patrice Vetsel (vetsel-patrice) wrote :

"That seems to not be a firefox bug." others persons believe the opposite. Is there a firefox hacker here ?!

And indeed this bug occur only at http://www.google.com/tools/firefox/ page

Revision history for this message
John Vivirito (gnomefreak) wrote :

Alexander i assigned htis to you to look at. My concern is that its only one site with a few extenstions on it that are failing as i understand it.

Changed in firefox:
assignee: freddymartinez9 → asac
Revision history for this message
Alexander Sack (asac) wrote : Re: [Bug 89071] Re: Can't allow sites for adding extensions

On Thu, Mar 08, 2007 at 04:43:27AM -0000, Patrice Vetsel wrote:
> "That seems to not be a firefox bug." others persons believe the
> opposite. Is there a firefox hacker here ?!
>
> And indeed this bug occur only at http://www.google.com/tools/firefox/
> page
>

this bug is known upstream and appears to be a regression from a
previous fix.

Upstream bug is: https://bugzilla.mozilla.org/show_bug.cgi?id=372819

 - Alexander

Changed in firefox:
assignee: asac → mozilla-bugs
status: Needs Info → In Progress
Revision history for this message
Alexander Sack (asac) wrote :

setting to confirm so I know that I should try to push upstream to do something about this.

Changed in firefox:
status: In Progress → Confirmed
Changed in firefox:
status: Unknown → Confirmed
Revision history for this message
In , Philringnalda (philringnalda) wrote :

Finally remembered to take my laptop to a better connection: yes, race condition (unless Google's insane enough to sniff connection speed and do different things, which I doubt but didn't check).

Over dialup, I get the install-blocked infobar with a broken edit button, and if I manually whitelist tools.google.com I get the install prompt; with the same build (and the same run-instance, for that matter) over a decent connection, I get the install prompt unless I remove addons.mozilla.org from the whitelist, in which case I get an infobar with a working edit button that adds amo.

Revision history for this message
In , Dveditz (dveditz) wrote :

We would like a fix for this, but we're not going to hold the release if we don't get it.

Alexander Sack (asac)
Changed in firefox:
importance: High → Undecided
status: Confirmed → In Progress
Revision history for this message
In , Enn (enndeakin) wrote :

Can't fix much here unless we have steps to reproduce.

Revision history for this message
In , Philringnalda (philringnalda) wrote :

Sorry if you don't like them, but comment 10 *is* STR - just add

0. Pinch your internet tubes down to 40Kbps or less.

to the STR from comment 0. Connected over dialup, I consistently 100% see the bug; hibernate, go to a faster connection, resume, I don't. I haven't seen Mr. Strong or the reporter say "oh, yeah, I was testing over a crappy-slow connection," but then I also haven't seen anyone else say "no, I went to my mom's with 28.8 AOL dialup, and I still don't see it there."

Revision history for this message
In , Robert-bugzilla (robert-bugzilla) wrote :

Neil, are you able to test by either simulating a slow connection or using a slow connection? This is 100% reproduceable for me when using a slow connection.

Revision history for this message
In , Enn (enndeakin) wrote :

(In reply to comment #14)
> Neil, are you able to test by either simulating a slow connection or using a
> slow connection? This is 100% reproduceable for me when using a slow
> connection.
>

I'm not really able to test that right now, no. Would be nice to get a reduced test here

Revision history for this message
In , Mike Connor (mconnor) wrote :

We need reliable STR here somehow. Moving to M9, does QA have any utilities for throttling network speed?

Revision history for this message
In , Dtownsend (dtownsend) wrote :

Note also that the edit options button is going away in bug 252830

Revision history for this message
In , Philringnalda (philringnalda) wrote :

I'm inclined to vote for WFM, or at least non-blocker. Google has made two significant changes since http://web.archive.org/web/20070202162244js_/tools.google.com/firefox/install.js - they now |setTimeout('addonsDown()', 3000)| instead of the previous 1000, and addonsDown() now directly sets the iframe .src to the XPI URL, instead of the previous (and uncached, so who knows what it was doing) http://tools.google.com/firefox/install2.html?theURLoftheXPI, and one or the other or both mean I can no longer reproduce the bug.

If you still want to fix it as an abstract problem, I think to reproduce you need a page equivalent to https://addons.mozilla.org/google/google_webcomments.html served with nocache headers so you don't wind up with it stuck in your cache, and another page that loads it in an iframe with an adjustable setTimeout() that changes the iframe .src, so you can find the number of milliseconds for your connection speed that will let the addons-equivalent page load and trigger the install, but then will change the iframe's src before the install code finishes checking. And then if reproducing also involves whatever install2.html used to do, I guess you'd have to ask Google what it was doing.

Revision history for this message
In , Mike Connor (mconnor) wrote :

moving out bugs that don't need to block b1

Revision history for this message
In , Dtownsend (dtownsend) wrote :

The edit options button now no longer exists, we appear to have no immediate way to test this so I can't say whether this is still a problem with the allow once button.

Revision history for this message
In , Mike Connor (mconnor) wrote :

Clearing blocking flag. If anyone can still reproduce this in some form, please renominate.

Revision history for this message
In , Mike Connor (mconnor) wrote :

Still may occur on branch, clearing TM.

Revision history for this message
In , Zoz (zoz) wrote :

( please excuse my english, i'm french )

I have the 2.0.0.14 version of Firefox on Windows xp

and i have the word: « modifier » on my menu, but it is not efficient !

I use to édit some pages before printing them ( when i print a page ) with my older version. I was deleting the items that i din't wont to appear on the print page.

But i can't do it anymore !

( But be aware thant i'm not very familiar with complicates download/reinstal actions on my pc. )

big tanks for your help ! if you can !

Revision history for this message
In , Dtownsend (dtownsend) wrote :

(In reply to comment #23)
> ( please excuse my english, i'm french )
>
> I have the 2.0.0.14 version of Firefox on Windows xp
>
> and i have the word: « modifier » on my menu, but it is not efficient !
>
> I use to édit some pages before printing them ( when i print a page ) with my
> older version. I was deleting the items that i din't wont to appear on the
> print page.
>
> But i can't do it anymore !

Your problems sound completely unrelated to this bug report. Please seek support before going to bugzilla: http://www.mozilla.org/support

Alexander Sack (asac)
Changed in firefox:
assignee: mozilla-bugs → nobody
status: In Progress → Triaged
Changed in firefox-3.0:
status: New → Triaged
Revision history for this message
In , Enn (enndeakin) wrote :

Don't think this is relevant any more.

Changed in firefox:
status: Confirmed → Invalid
Revision history for this message
Micah Gersten (micahg) wrote :

No more fixes for Firefox 2.

Changed in firefox (Ubuntu):
status: Triaged → Won't Fix
Revision history for this message
Micah Gersten (micahg) wrote :

Per upstream, and my own tests, this no longer appears to be an issue. If you are still experiencing, trouble, you can change the status back to New and provide more information as to your current version of Firefox and what exactly is not working.
Please feel free to report any other bugs you may find.

Changed in firefox-3.0 (Ubuntu):
status: Triaged → Invalid
Changed in firefox:
importance: Unknown → Medium
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.