Ok, funky is back.
> Well I restarted my browser to clear the extra infobars, and all of
> the funky things I described here went away. The only remaining
> problem is there does not seem to be a way to use the JS debug on
> infobars. You can't open the debugger until the infobar is open, and
> then the script has already completed.
> jjb
> On Dec 13, 3:57 pm, johnjbarton <johnjbar...@johnjbarton.com> wrote:
> > I managed to get this feature to sorta work in my extension. However
> > the documentation says
> > "The infobar will be closed automatically when the tab navigates. Use
> > window.close() to close the infobar before then."
> > So to close the infobar process you have to send it a message to call
> > window.close() on itself?
> > I currently have 10 infobars listed in my extension "Inspect active
> > views". Is there any way to get rid of them short of exiting the
> > browser? I tried closing the window I added the infobar to and I tried
> > reload and enable/disable on my extension, no luck.
> > BTW a cool interaction between the many copies of infobar windows and
> > debugging: if you click on one of the infobar urls you launch one copy
> > of the Devtools for each open infobar. So like 12 little Web
> > Inspectors ;-).
> > Finally: will the performance improve? The infobar comes up laggy
> > jjb
