Tab Mix Plus

 
TMP 0.4.0.2pre.120407b

One thing that still annyos me,

if I set new tab to Blank Page (extensions.tabmix.loadOnNewTab.type = 0)
OR
New Tab Page: "about:blank" (extensions.tabmix.loadOnNewTab.type = 4)
AND
if "Prevent last tab from closing" is disabled (extensions.tabmix.keepLastTab = false)

when I close the last tab OR close all tabs, I got "about:newtab" instead of "about:blank"
and when I close it (the "about:newtab"), it's added to "Recently closed tabs" list.

_________________
Mozillian profile | AMO profile

LouC, did you read the thread? or the installation confirmation page?

_________________
VistaHP/Fx latest beta/TMP latest dev.build/Troubleshooting TMP/My styles

 
Yes.
 

_________________
Mozillian profile | AMO profile

So, are you complaining about the Blank Page option being switched to :newtab or that it was added to the closed tabs list?

See, my whole rant here and the dev.build thread is about TMP changing MY settings. IMO, regardless of what Fx does, TMP should detect MY settings and retain it. I don't know if this was possible or not but i do know there'll be a lot of people wondering. IMO, it was enough to place that info (see above) on the confirmation page and leave our settings alone.

EDIT: of course, i mean the information about the new way Fx does new tab option, the rest would've been irrelevant if our settings would've been preserved.

_________________
VistaHP/Fx latest beta/TMP latest dev.build/Troubleshooting TMP/My styles

 
OK, I'll be there.
Thanks.
 

_________________
Mozillian profile | AMO profile

 
Sorry. It's actually Firefox's fault.
I've filed ̶b̶u̶g̶ ̶7̶4̶3̶5̶6̶1̶ ̶–̶ ̶a̶b̶o̶u̶t̶:̶n̶e̶w̶t̶a̶b̶ ̶s̶h̶o̶u̶l̶d̶ ̶n̶o̶t̶ ̶b̶e̶ ̶a̶d̶d̶e̶d̶ ̶t̶o̶ ̶R̶e̶c̶e̶n̶t̶l̶y̶ ̶C̶l̶o̶s̶e̶d̶ ̶T̶a̶b̶s̶ ̶l̶i̶s̶t̶ ̶w̶h̶e̶n̶ ̶i̶t̶'̶s̶ ̶c̶l̶o̶s̶e̶d̶
edit: dupe of bug 717044 – Session store should be aware of browser.newtab.url

edit:
I just found out about this pref extensions.tabmix.replaceLastTabWith.newtab.url
Set its value to about:blank solved my problem.

Thanks

_________________
Mozillian profile | AMO profile

makondo

we should change the installation page comment to indicate that the change apply to "Load on new tabs..." and "When i close last tab replace it with..."

_________________
Tab Mix Plus 0.4.1.0
latest Dev-Build
Forum RSS, Troubleshooting

Awesome find, LouC! Thanks a whole bunch 12x12!

But it should've been onemen posting this when i first started to boil

onemen,
give me the link to the confirm.page, i didn't save it.

_________________
VistaHP/Fx latest beta/TMP latest dev.build/Troubleshooting TMP/My styles

_________________
Tab Mix Plus 0.4.1.0
latest Dev-Build
Forum RSS, Troubleshooting

Important note for Firefox 12+ users
Starting with Firefox 12, Tabmix default for "Load on new tabs" option changed to New Tab Page. When you update Firefox to v.12, it resets Tabmix option to New Tab Page and you have to make your selection again under Events/New tab. You have a few options if you had the Blank Page option selected previously:

re-set Tabmix to load Blank Page.
use the New Tab Page for new tabs.
use the New Tab Page but disable it by clicking on the button on the upper right corner, this will turn the New Tab Page into blank page for new tabs.
(or setting browser.newtabpage.enabled to false)
set Tabmix to load the New Tab Page and set the address to about:blank.

This change effects settings for the "When i close last tab replace it with..." option under Events/Tab closing.

_________________
VistaHP/Fx latest beta/TMP latest dev.build/Troubleshooting TMP/My styles

BTW, mine wasn't changed, as far as i know. I mean, i didn't change it, it still shows Blank page for me and i didn't touch it (Events/Tab closing).

_________________
VistaHP/Fx latest beta/TMP latest dev.build/Troubleshooting TMP/My styles

Interesting debate...

There are as you may be aware a number of extensions that run in about:blank
Fastdial is just one of them.

Quote taken from this page of Jorge Villalobos
http://blog.mozilla.com/addons/2012/03/ ... irefox-12/
"This overlaps with the features of several existing add-ons, so some breakage is to be expected."

Now this approach obviously causes a dilemma, as there is no middle ground.
It is not saying please try our new tab feature by going to these settings here and changing.....

So an extension that has run for many years for it's users in about:blank then faces immediate and sudden "breakage"

It is clear then at that point that either FNTF wipes out the Extension or the Extension causes Firefox to return to about:blank. This is necessary in order for the extension to survive.

All well and good.

On this page
http://timtaubert.de/2012/02/help-us-te ... -tab-page/
We have Tim Taubert responding to a an excellent point by Eric Shepherd
"We’re thinking about having a drop-down menu in the Preferences dialog that lets you choose the url for the new tab page."

If this is all done in a clear manner by Firefox as suggested, then this will give the user who is used to running in the about:blank page the possibility of toggling if he so wishes to look at FNTF should he so chose.

So this change could be made without the use of TMP
But in a way TMP obviously lends itself to be a perfect candidate for toggling settings as well

But what if TMP then also want to get into the fray, that is by deciding which way users of TMP (who may of course be running other extensions ) should go, then that complicates the whole issue somewhat further.

I suppose I would like to suggest that TMP gives thought to the different issues involved and tries to take a position of neutrality.

The trouble with the situation being presented by Firefox at the moment is either you are with us or against us.

I think many users (like makondo) would like to feel that they have the absolute right to autodetermination, and that they do not want to be steered by force in a direction that is not of their choosing.
This would be especially true of users who have always made active use of the about:blank page

This a most regrettable situation and creates an unwelcome ethos.

I hope at least that between Fast Dial and TMP some elegant solution could be deliberated.

_________________
Windows XP Home--Firefox 15.0.1--Tab Mix Plus 0.4.0.4pre.120724a--Fast Dial 4.2.2-- Flash Video Downloader - Youtube Downloader 3.6.8 (later changed to Version 3.6.9 !! which works)

I will do some tests my end to see if there are any problems in reality and report back here.
Have you made any tests yourself on this issue ?

My interest in the previous post was really to raise the question, in case problems might arise further down the line.

many thanks

_________________
Windows XP Home--Firefox 15.0.1--Tab Mix Plus 0.4.0.4pre.120724a--Fast Dial 4.2.2-- Flash Video Downloader - Youtube Downloader 3.6.8 (later changed to Version 3.6.9 !! which works)

Have made perliminary tests, will post findings later, but it would seem in fact that even if the default settings would seem to point to newtab in TMP, that TMP also seems to adapt to changes in the URL setting and does not intervene.

This is very good news.

It would seem then that there is at this point then no conflict between the extensions.

many thanks

_________________
Windows XP Home--Firefox 15.0.1--Tab Mix Plus 0.4.0.4pre.120724a--Fast Dial 4.2.2-- Flash Video Downloader - Youtube Downloader 3.6.8 (later changed to Version 3.6.9 !! which works)

Settings with TMP loaded



Load extension which modifies New Tab Page to about:blank




So TMP it would seem respects any alteration of the New Tab Page setting by the user to about:blank even though this change has not been made from within TMP.
TMP does not overide this new setting.



We hope to set up a tuition page for Fast Dial users to let them know how they can use TMP to toggle settings in regard to the New Tab Page. This will be very useful.

Many thanks TMP

It would seem that my earlier concerns for a possible conflict were quite unfounded
My apologies...

_________________
Windows XP Home--Firefox 15.0.1--Tab Mix Plus 0.4.0.4pre.120724a--Fast Dial 4.2.2-- Flash Video Downloader - Youtube Downloader 3.6.8 (later changed to Version 3.6.9 !! which works)