One minor thing we are already doing is updating the tabs API to make this thing a bit easier:
http://code.google.com/p/chromium/issues/detail?id=21729 I'm interested in hearing ideas on how to make keeping tab-specific state easier though. For people who are running into this, what does your ideal API look like? - a On Fri, Oct 2, 2009 at 3:33 PM, Matias Pelenur <[email protected]> wrote: > > I'm writing an extension that uses the toolstrip mole > (chrome.toolstrip.expand/collapse) functionality to pop up on certain > pages. The user can also minimize/expand it on demand on those pages. > > Since toolstrips are per window, and not per tab, I need to keep a > good amount of state in the background page, and coordinate between > the background page and the toolstrip quite a bit. For example, if the > user moves from a tab where the toolstrip is showing to one where it's > not, the background page needs to tell the toolstrip to collapse > itself, and vice-versa. Letting the user also collapse and expand > means that the background page needs to know that too. > > All this gets fairly complicated and bug-prone, and it seems that my > extension will not be the only one to have this use case of per-tab > toolstrip state. Would the Chrome extensions team consider adding > support for this to the API? I could come up with a more defined > proposal. > > Thanks, > matias > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Chromium-extensions" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/chromium-extensions?hl=en -~----------~----~----~----~------~----~------~--~---
