Chrome 22 and limits on number of open tabs

875 views
Skip to first unread message

Andrei Vasilescu

unread,
Sep 17, 2012, 2:26:14 AM9/17/12
to chromium...@chromium.org
Hello everyone,

My team has heard from our users that early adopters of Chrome 22 experiment a strange behavior: our application allows them to open multiple tabs all by issuing one command and now they are limited to opening at most two new tabs each time they run this shortcut.

Has anyone seen something similar? Is this a new feature of the upcoming beta release? Is it somehow tweakable or is our application doing something that is deemed offensive?

People actually are using this feature to open multiple data entry pages and close each one as they finish doing what is requested on each one. This is an older application and I would hope to find a quick answer for this problem with hopefully little required modifications.

Thanks,
Andrei

Andrei Vasilescu

unread,
Sep 17, 2012, 2:33:36 AM9/17/12
to chromium...@chromium.org
A few more details... our users are reporting that version 22.0.1229.26 is still allowing opening countless tabs, while people already on 22.0.1229.39 and 22.0.1229.52 (on Linux) are seeing the limitation of open tabs.

PhistucK

unread,
Sep 17, 2012, 3:52:09 AM9/17/12
to andr...@google.com, chromium...@chromium.org
So, opening more than two tabs using the command line no longer opens more than two tabs?
(If so, a quick and dirty workaround might be to create a Chrome extension that chrome.tabs.create all of these tabs when you go to a certain entry point page (observe the creation of the entry point page using chrome.tabs.onCreated), which would be the first and/or second URLs provided by the command line).
Or are you using window.open to open the other tabs?


PhistucK



--
Chromium Discussion mailing list: chromium...@chromium.org
View archives, change email options, or unsubscribe:
http://groups.google.com/a/chromium.org/group/chromium-discuss

Andrei Vasilescu

unread,
Sep 17, 2012, 4:06:53 AM9/17/12
to PhistucK, chromium...@chromium.org
Hi Alon,

Yes, I am using window.open. The actual call is made by the closure JS
library (which seems to have been around for a long time):
https://cs.corp.google.com/#google3/javascript/closure/window/window.js&q=goog.window&type=cs&l=80
and a sample call like: goog.window.open(url, {'target': '_blank'});

Thanks,
Andrei

PhistucK

unread,
Sep 17, 2012, 4:11:09 AM9/17/12
to Andrei Vasilescu, chromium...@chromium.org
Does the normal window.open exhibit the same behavior? or does only the Closure based call exhibit this behavior?

You can search crbug.com for an existing issue and star it. If you cannot find one, file a new issue at new.crbug.com and attach a reduced test case.
Please, do not add a "+1" or "Me too" or "Confirmed" (or similar) comment. It just wastes the time of Chrome engineers and sends unnecessary e-mails to all of the people who starred the issue.

When you are done, post a link to the relevant/created issue here.

Thank you.

PhistucK

Joshua Redel

unread,
Sep 26, 2012, 5:54:49 PM9/26/12
to chromium...@chromium.org, Andrei Vasilescu
We're having the same or a similar issue, in that a tool we use on chrome only opens two windows when we touch a hotkey, considering all the other windows to be pop-ups. Either they are blocked by pop-up blocker or are opened as separate pop-up windows (i.e. can't be used like tabs).

John Bell

unread,
Oct 2, 2012, 8:18:41 AM10/2/12
to chromium...@chromium.org
I'm having the exact same problem, I have to verify hundreds of sites each day for one of my websites and I created a script to open 20 pages at a time in new tabs and it was working as expected as well as working cross-browser, however now the first 2 will open in tabs and the rest all open in windows, making chrome useless for this task

Rick LaBanca

unread,
Oct 10, 2012, 5:47:28 PM10/10/12
to chromium...@chromium.org

I'm hitting this also, with a commercial site that does popups, user selected via checkboxes. 

ainu7

unread,
Nov 18, 2012, 7:41:14 PM11/18/12
to chromium...@chromium.org
The problem still persists. Does someone follow this issue?

2012년 10월 11일 목요일 오전 6시 47분 29초 UTC+9, Rick LaBanca 님의 말:

erosonog

unread,
Jan 19, 2013, 12:44:33 PM1/19/13
to chromium...@chromium.org
I am suffering from the same problem.
The issue has been reported as Issue 155841 in crbug.com.

Reply all
Reply to author
Forward
0 new messages