Closed Bug 1695248 Opened 4 years ago Closed 3 years ago

Migrate users with browserconfig.properties set as their home page

Categories

(Firefox :: New Tab Page, task)

task

Tracking

()

RESOLVED FIXED

People

(Reporter: zbraniecki, Unassigned)

References

()

Details

In bug 721211 we removed browserconfig.properties file that was used as a home page for localized builds.

The new telemetry of UI resource network loads shows that we still have a substantial number of users who trigger the attempt to load omni.ja!/chrome/en-US/locale/branding/browserconfig.properties.

We see ~3k events per day on Beta (1.1k clients per day). It's hard to predict how it'll translate on Release, but for most of YSOD research the volume of errors translates at ~20x which would indicate 60k/day.

I suspect a migration of browserconfig.properties in home page / new tab prefs.js could help those users.

See Also: → 1490339

The Bugbug bot thinks this bug should belong to the 'Core::Networking' component, and is moving the bug to that component. Please revert this change in case you think the bot is wrong.

Component: General → Networking
Product: Firefox → Core
Component: Networking → New Tab Page
Product: Core → Firefox

I can now confirm that we're seeing ~34-40k clients a day with that problem - https://sql.telemetry.mozilla.org/queries/79329/source#197050

Bug 1728854 in 94 might shift some users off this custom pref value as the default flow will have users reset their home page to about:home.

See Also: → 1728854

This is now fixed, we see below 40 events per day down from 40k per day 7 months ago.

Status: NEW → RESOLVED
Closed: 3 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.