1443646 - Figure out what to do with browser.newtabpage.enabled pref

Status: RESOLVED DUPLICATE of bug 1383599

(Firefox :: New Tab Page, defect)

Description

[:Gijs (he/him)]

IME on 59 this pref does absolutely nothing. But toolkit's newtabutils still checks it, so perhaps there's some use for it with custom new tab pages. It's hard to tell off-hand. I'm leaving it be in bug 1433133 for simplicity's sake.

Comment 1

[Ed Lee :Mardak]

I believe it's unused right now… I suggested in bug 1383599 comment 9 that we could repurpose the old pref as an intent to not see any content for new tabs. And with bug 1417155, there would be a Home panel drop down UI to allow selecting a "blank page" option for new tabs. I wonder if this is something we should get in for ESR60? And unless someone knows of what .enabled is currently used for, perhaps just dupe this bug to 1383599 or resolve

Comment 2

[Hlsg]

(In reply to Ed Lee :Mardak (PTO-Mar18) from comment #1)
> I believe it's unused right now… I suggested in bug 1383599 comment 9 that
> we could repurpose the old pref as an intent to not see any content for new
> tabs. And with bug 1417155, there would be a Home panel drop down UI to
> allow selecting a "blank page" option for new tabs. I wonder if this is
> something we should get in for ESR60? And unless someone knows of what
> .enabled is currently used for, perhaps just dupe this bug to 1383599 or
> resolve

Indeed, when switching to ESR60, I'm sure there'll be plenty of unhappy people regarding the inability to point to about:blank. Using this pref would make sense for that purpose.

Comment 3

[Ed Lee :Mardak]

I ended up removing the prefs.js comment referring to this bug as it's now in use again with bug 1383599 and will get UI exposed in bug 1417155.