Right. As I was saying, this is by design. If you want to persist state, put it in a background page (you can put iframes there as well) and then just proxy the UI over to the popup as needed.
Erik On Thu, Dec 3, 2009 at 12:41 AM, Bruno <[email protected]> wrote: > That's what I want to point out. > When we want to create an extension using an iframe, this will be > deleted when the popup is closed. > So it's currently impossible to create a gtalk extension with the > gadget (for exemple), the iframe is destroy on each close and logout > from gtalk. > > > On Dec 3, 12:56 am, Erik Kay <[email protected]> wrote: > > -chromium-discuss > > +chromium-extensions (this is where extensions discussions and questions > > should be sent) > > > > On Wed, Dec 2, 2009 at 3:24 AM, Bruno <[email protected]> wrote: > > > Hi! > > > > > Currently, when we've configured a popup linked to the BrowserAction, > > > every click on the button reload the page. > > > 2I suggest that this popup just reloaded on each click but once on > > > window initialization. > > > I think there is already an event handler for clicks on BrowserAction, > > > then people who need the reload do not have problems > > > > The popup gets completely destroyed when it's dismissed. It doesn't > persist > > across clicks. If you'd like to have some precomputed state that you > load > > into your popup, just use a background page. That doesn't get destroyed > > until Chrome exits. > > > > Erik > > > > > > > > > > > > > Bruno > > > > > -- > > > Chromium Discussion mailing list: [email protected] > > > View archives, change email options, or unsubscribe: > > > http://groups.google.com/group/chromium-discuss > > -- > Chromium Discussion mailing list: [email protected] > View archives, change email options, or unsubscribe: > http://groups.google.com/group/chromium-discuss > -- Chromium Discussion mailing list: [email protected] View archives, change email options, or unsubscribe: http://groups.google.com/group/chromium-discuss
