I have a feature request for Chrome extensions and wondering where I
should go with it.
I have an extension (
https://chrome.google.com/webstore/detail/
pnjaodmkngahhkoihejjehlcdlnohgmp), it's basically an RSS reader within
the popup. Many of my users (including me) want to be able to read
feeds and not have to close the popup every time a new tab is created
from clicking a post. In Chrome < 19 this wasn't a problem for me (on
Mac OS X), since opening a new tab (chrome.tabs.create) from within
the popup didn't close it, letting me browse and read my feeds while
the popup was open. With Chrome 19 came a rewrite of the popup (I
assume) that makes it impossible to keep the popup open when opening
new tabs. Before 19 you could hack it by setting
chrome.tabs.create({selected: false, active: true}) or something like
that, but it didn't display the tab new tab. A corner case basically.
So my idea is to add a method to the chrome.browserAction object:
chrome.browserAction.lock() and
chrome.browserAction.unlock()
Which would keep the popup from closing when losing focus, and also a
method for unlocking it. So the user can navigate tabs, scroll on
pages and click on links and the popup wouldn't disappear. (When the
popup should closed is a bit vague still, perhaps add a X-button the
popup for force closing it) Only one popup can be visible at a time.
I have been talking to the developer of RSS Live Links too, (https://
chrome.google.com/webstore/detail/hcamnijgggppihioleoenjmlnakejdph)
who also has had to hack around the issue. With Chrome 19 has had to
make a complete work-around. I can think of other use cases for being
able to lock the popup, so I sincerely believe that there will be a
use for this.
Right now there are a couple of bug tickets for the popup and closing
when losing focus:
http://code.google.com/p/chromium/issues/detail?id=111094 Where most
people seem to agree that there should be some degree of control as to
when the popup should close
http://code.google.com/p/chromium/issues/detail?id=110377 Where the
opposite appears to be expected in Chrome OS, but I assume that its
because it doesn't work the same as on all the other platforms.
My question is also: Where do I go with this? I want to start a
discussion about adding more control to the browserAction popup, since
there is little-to-none right now, and it is seriously impeding the
developers and usability of the browserAction popup.
Thanks