Commentary

Mitch Wagner
Executive Editor, Community  

How To Stop Firefox From Blocking Google Reader Popups

I just found a solution to a problem that was driving me crazy for months, and I'm passing it along now for my fellow sufferers. Firefox was blocking popups in Google Reader, even though I explicitly told Reader to allow popups for the entire domain Google.com. Turns out this isn't a bug (as the programmer joke goes), it's a feature. Read on for the fix.

I just found a solution to a problem that was driving me crazy for months, and I'm passing it along now for my fellow sufferers. Firefox was blocking popups in Google Reader, even though I explicitly told Reader to allow popups for the entire domain Google.com. Turns out this isn't a bug (as the programmer joke goes), it's a feature. Read on for the fix.First, I'll describe the problem. I use Google Reader to view hundreds of articles every day, collected from dozens of Web sites. I use the keyboard to navigate: Space bar to move from one item to the next, and the V key to open an article on the original site. That V key gets a good workout; many sites, like InformationWeek, only put excerpts in the RSS feed, and you have to go to the original site to read the entire article.

Firefox's normal behavior is to block popups. However, it's easy enough to whitelist domains where you want popups to appear, like Google.com.


More Internet Insights

White Papers

More >>

Reports

More >>

Webcasts

More >>

Months ago, I noticed a bug: After I'd been using Google Reader for more than a half-hour or so in any individual session, Firefox started blocking popups on the site. I checked to see if I'd configured my whitelist correctly, and I had. Firefox was supposed to be allowing popups from Google, but it was blocking them. Re-starting the browser fixed the problem, but that was inconvenient, and it only fixed the problem for a while -- it would recur after another half-hour or so.

Turns out that's a design feature of Firefox. A person signing himself Graham, the Google Reader Guide, explains:

Apparently there's a limit on the number of popups that a site can have, even if you've designated it as an "allowed" site for popups in Firefox. So if you are using the "v" key for dozens of articles in Reader, you might hit that limit. Restarting the browser resets the count. But if, like me, you run into this limit a lot, you can actually change it:

1. In a Firefox window, enter "about:config" in the address bar.
2. In the "Filter" field, type "popup_maximum".
3. One preference, called "popup_maximum" appears; double-click the "value" number.
4. Enter a new, appropriately large value. I used 2000, just to be on the safe side.

Now Firefox will give any "allowed" sites even more free rein with popups and you should be able to "v" away happily without interruption.

I tried the fix and it works! Thanks, Graham! Hopefully, if you've been having the same annoying problem, this fix will work for you, too.


Related Reading




Currently we allow the following HTML tags in comments:

Single tags

These tags can be used alone and don't need an ending tag.

<br> Defines a single line break

<hr> Defines a horizontal line

Matching tags

These require an ending tag - e.g. <i>italic text</i>

<a> Defines an anchor

<b> Defines bold text

<big> Defines big text

<blockquote> Defines a long quotation

<caption> Defines a table caption

<cite> Defines a citation

<code> Defines computer code text

<em> Defines emphasized text

<fieldset> Defines a border around elements in a form

<h1> This is heading 1

<h2> This is heading 2

<h3> This is heading 3

<h4> This is heading 4

<h5> This is heading 5

<h6> This is heading 6

<i> Defines italic text

<p> Defines a paragraph

<pre> Defines preformatted text

<q> Defines a short quotation

<samp> Defines sample computer code text

<small> Defines small text

<span> Defines a section in a document

<s> Defines strikethrough text

<strike> Defines strikethrough text

<strong> Defines strong text

<sub> Defines subscripted text

<sup> Defines superscripted text

<u> Defines underlined text

InformationWeek encourages readers to engage in spirited, healthy debate, including taking us to task. However, InformationWeek moderates all comments posted to our site, and reserves the right to modify or remove any content that it determines to be derogatory, offensive, inflammatory, vulgar, irrelevant/off-topic, racist or obvious marketing/SPAM. InformationWeek further reserves the right to disable the profile of any commenter participating in said activities.

Disqus Tips To upload an avatar photo, first complete your Disqus profile. | View the list of supported HTML tags you can use to style comments. | Please read our commenting policy.
T-Shirt Giveaway T-Shirt Giveaway: Each week we're selecting one great comment from our readers. The author of the comment will receive an InformaitonWeek Community t-shirt. So get posting!
Subscribe to RSS

Resource Links