Change the default setting for pull-to-refresh to disabled again
Categories
(Firefox for Android :: Browser Engine, task, P1)
Tracking
()
People
(Reporter: cpeterson, Assigned: polly)
References
Details
Attachments
(1 file, 1 obsolete file)
Due to PTR bugs blocking meta bug 1882722 and user reports of problems, we should change PTR's default back to disabled. We previously disabled PTR by default in Fx 116 (bug 1847282) and then re-enabled it in Fx 124 (bug 18795830).
Can we selectively leave PTR enabled for users that manually enabled it in Fx <= 123 before we enabled by default for everyone in Fx 124 (bug 18795830)? Users who manually enabled it know what PTR is and how to find the setting to turn it on and off. If they were unhappy with PTR bugs, they would presumably turn it off.
If we can't selectively enable or disable it for some users, we should disable it for everyone. Users who know what PTR is can find the setting to turn it back on.
| Assignee | ||
Comment 1•1 year ago
•
|
||
Doesn't look like we have any way of knowing what a user's historical preference settings have been. So we would need to disable the feature by default for everyone.
If we make pull-to-refresh default to false for release builds, pull-to-refresh will be turned OFF for:
- release build new installs
- release build existing installs where the user has not interacted with the settings switch (which I think would include most people)
Pull-to-refresh will remain ON for:
- nightly / dev build new installs
- nightly / dev build existing installs where the user has not interacted with the settings switch
- release build existing installs where the user has switched pull-to-refresh on
| Assignee | ||
Updated•1 year ago
|
| Assignee | ||
Comment 2•1 year ago
|
||
Updated•1 year ago
|
| Assignee | ||
Comment 3•1 year ago
•
|
||
This is stored separately to the main switch setting - as we sometimes manipulate that to turn the pull-to-refresh feature on or off by default. (we don't need this extra switch - we can use the default value to get this behaviour)
In the future, this could help us find users who want to use pull-to-refresh even if other users are experiencing issues, and not disable the feature for them.
Updated•1 year ago
|
Updated•1 year ago
|
Comment 5•1 year ago
|
||
| bugherder | ||
Updated•1 year ago
|
Description
•