So, i just discovered that if i put the function that does the chrome.tabs.update in, e.g., my background.html and call it in popup.html with chrome.extension.getBackgroundPage().openURL() it works just as expected, so i guess it's something in my popup.html that breaks it somehow. Any ideas?
On 2 Dec., 18:22, ChrisBuchholz <[email protected]> wrote: > I cannot even create a new bug at crbug.com, because I cant find any > logic or valid data to explain the bug. > It seems so unlogical and weird, because it is only in that exact > context it happens, and only when I use chrome.tabs.update(_tabid_, > {_something_}) - without any update properties, it doesn't crash. If i > try with e.g. chrome.tabs.remove(_tabid_) it also works perfectly. I > have tried setting it out of context, creating a whole new function > with chrome.tabs.update in a whole other scope, but that also crashes. > It actually seems, that it is every time the function containing the > chrome.tabs.update gets triggered from the event it does, that the > crash happens, because if I try in another layer with a similar form, > it does work. > A conclusion would be, that it is the triggering event that is the > reason (although, it first when chrome.tabs.update gets called it > crashed) to the crash. > > Here is the whole extension - the chrome.tabs.update that crashes is > in popup.html:sources.openURL() and the event triggered it is in > popup.html:line:46 > Maybe someone could give it a spin, and get back with some thoughts on > the problem. > > http://dl.dropbox.com/u/168187/Google%20alerter.zip > > It's still a problem on 4.0.249.29. > > > > > On 2 Dec., 00:39, Antony Sargent <[email protected]> wrote: > > I didn't see anything that looks like the same thing with a quick search of > > crbug.com. Could you create a new bug including the code you have that > > reproduces this, and reply here with the bug id? > > >http://crbug.com/new > > > Thanks! > > > On Tue, Dec 1, 2009 at 2:14 AM, ChrisBuchholz < > > > [email protected]> wrote: > > > Hi, > > > > I'm using chrome.tabs.update to select a tab, but when executed, the > > > extension first crashes and then takes chrome down with it: > > > > chrome.tabs.update(tabs[i].id, {selected: true}); > > > > Surely, tabs[i].id does in fact contain a numeric value. > > > I have only been able to test this on Google Chrome 4.0.249.11 on > > > Windows XP, but I will give it some more testing (on different > > > platforms and also with Chromium) when I get home later today. > > > > Is it a known bug? > > > > -- > > > > 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]<chromium-extensions%2Bunsu > > > [email protected]> > > > . > > > For more options, visit this group at > > >http://groups.google.com/group/chromium-extensions?hl=en. -- 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.
