Re: Stop Firebug opening new tab after update
492 views
Skip to first unread message
Jan Honza Odvarko
Oct 10, 2012, 2:24:10 AM10/10/12
to Firebug
On Oct 9, 11:30 pm, Paul Renold <slug...@gmail.com> wrote:
> Now that Firefox does silent updates to extensions while running I'm
> starting to get annoyed when extensions like Firebug open a new tab after
> they have been updated. It was one thing to get a new tab or two when
> opening Firefox after an update, but now they open in the middle of
> browsing sessions. Worse yet the new tabs open in the foreground,
> disturbing whatever I was browsing before. Very annoying if you're in the
> middle of a video or a game.
This problem is being solved in this report:
http://code.google.com/p/fbug/issues/detail?id=5888
(should be fixed in the next release)
> So, any way to stop Firebug (and maybe extensions in general) opening a new
> tab after an update?
Yes, you can disable it entirely. Just go to about:config and set
extensions.firebug.showFirstRunPage preference to false.
Honza
> Now that Firefox does silent updates to extensions while running I'm
> starting to get annoyed when extensions like Firebug open a new tab after
> they have been updated. It was one thing to get a new tab or two when
> opening Firefox after an update, but now they open in the middle of
> browsing sessions. Worse yet the new tabs open in the foreground,
> disturbing whatever I was browsing before. Very annoying if you're in the
> middle of a video or a game.
This problem is being solved in this report:
http://code.google.com/p/fbug/issues/detail?id=5888
(should be fixed in the next release)
> So, any way to stop Firebug (and maybe extensions in general) opening a new
> tab after an update?
Yes, you can disable it entirely. Just go to about:config and set
extensions.firebug.showFirstRunPage preference to false.
Honza
Jan Honza Odvarko
Oct 10, 2012, 10:06:10 AM10/10/12
to Firebug
On Oct 10, 3:55 pm, DCStone <dst...@chem.utoronto.ca> wrote:
> So are you saying that, in the next release, the tab will open *behind* the
> current tab?
No
It would turn off the update tab completely.
> If so, that would be great: I'd rather not turn off the update tabs
> completely. It's not
> just FireBug that does this, either - WebDeveloper toolbar extension does
> it also.
> Is that because both are using the same mechanism i.e. is there one fix for
> all
> update tabs?
AFAIK, every extension does this itself.
There were some discussions in the past about new Firefox platform API
that would
(at least) allow to share one update page by all extensions, but I
don't think
it actually happened...
Honza
> So are you saying that, in the next release, the tab will open *behind* the
> current tab?
No
It would turn off the update tab completely.
> If so, that would be great: I'd rather not turn off the update tabs
> completely. It's not
> just FireBug that does this, either - WebDeveloper toolbar extension does
> it also.
> Is that because both are using the same mechanism i.e. is there one fix for
> all
> update tabs?
AFAIK, every extension does this itself.
There were some discussions in the past about new Firefox platform API
that would
(at least) allow to share one update page by all extensions, but I
don't think
it actually happened...
Honza
Sebastian Zartner
Oct 10, 2012, 4:49:13 PM10/10/12
to fir...@googlegroups.com
On Oct 10, 3:55 pm, DCStone <dst...@chem.utoronto.ca> wrote:
> So are you saying that, in the next release, the tab will open *behind* the
> current tab?
No
It would turn off the update tab completely.
What Honza means is that setting the preference extensions.firebug.showFirstRunPage to false will turn off the update tab aka first-run page completely.
In the next release there will be a solution to avoid interrupting the workflow with the browser. How this is done is discussed in issue 5888.
Sebastian
In the next release there will be a solution to avoid interrupting the workflow with the browser. How this is done is discussed in issue 5888.
Sebastian
Reply all
Reply to author
Forward
0 new messages