1271727 - Firefox should allow you to set New Tab to certain fixed values

Status: RESOLVED WONTFIX

(Firefox :: New Tab Page, enhancement)

Description

[u552789]

From Firefox 41 one is now unable in about:config to set the New Tab to a custom URL, and as far as I remember this is due to certain security issues with New Tab hijacking.

So before one could set it to any URL, now one cannot set it to anything, but I think that something in between would be better, so I propose that one is allowed to set the New Tab URL in about:config to certain fixed values. Probably it would allow you to set it to:

- about:newtab (Default New Tab page)
- about:blank (Blank page)
- about:home (Default Firefox home page)

But nothing else so there shouldn't be any security issues around New Tab hijacking. Another thing to add, if this does get implemented then I think that the settings should also be accessible through about:preferences and not just about:config as these are essential settings like the home page and will be useful for all users and not just advanced ones.

I originally filed a report on this issue here but thought I should also do so upstream: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1580274

Comment 1

[alex_mayorga]

[Tracking Requested - why for this release]:

¡Hola Nikita!

I ended up here while investigating on https://support.mozilla.org/questions/1174370

https://addons.mozilla.org/firefox/addon/newtaburl/ apparently provided a fix but per the most recent comments and compatibility details it has stopped working since around Firefox 41.

Hope this helps.

Confirming per the SuMo question.

¡Gracias!
Alex

Comment 2

[u552789]

This is now allowed in about:preferences#home. So as this feature has now been implemented please mark as "FIXED".

Comment 3

[u552789]

Whoops! Didn't mean to close the bug! It would really be better if it was given proper status. Rather than what a standard user can give it.

Comment 4

[Jessilyn Davis]

Hello!

This bug has been closed due to inactivity and/or the potential for this bug to no longer be an issue with the new Discovery Stream-powered New Tab experience.

Please help us triage by reopening if this issue still persists and should be addressed.

Thanks!