-
Notifications
You must be signed in to change notification settings - Fork 2.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Update default widget list for desktop #19708
Labels
feature/widgets
OS/Desktop
priority/P3
The next thing for us to work on. It'll ride the trains.
QA Pass-Linux
QA Pass-macOS
QA Pass-Win64
QA/Test-All-Platforms
QA/Yes
release-notes/include
Milestone
Comments
simonhong
changed the title
Hide crypto widgets by default
Hide crypto widgets by default on desktop
Nov 24, 2021
24 tasks
simonhong
added a commit
to brave/brave-core
that referenced
this issue
Nov 24, 2021
fix brave/brave-browser#19708 Migration is done once in the first NTP loading. For new users, all crypto widgets are hidden by default. For existing users, if current foremost widget is crypto widget, only it is visible and others are hidden. After migration, user can control crypto widget's visibility from gallery. To make all crypto widgets hidden by default, each pref's default value is not changed. Their default prefs is still "true". As their visibility are managed by prefs and widget order is managed in local storage, it's difficult to start migration from c++. If default is changed to false, it's very difficult to determine whether foremost widget is crypto or not in the NTP webui.
rebron
added
the
priority/P3
The next thing for us to work on. It'll ride the trains.
label
Nov 24, 2021
simonhong
added a commit
to brave/brave-core
that referenced
this issue
Nov 25, 2021
* Migrate crypto widgets visibility in NTP fix brave/brave-browser#19708 Migration is done once in the first NTP loading. For new users, all crypto widgets are hidden by default. For existing users, if current foremost widget is crypto widget, only it is visible and others are hidden. And, authed widgets are visible regardless of its position in widget stack After migration, user can control crypto widget's visibility from gallery. To make all crypto widgets hidden by default, each pref's default value is not changed. Their default prefs is still "true". As their visibility are managed by prefs and widget order is managed in local storage, it's difficult to start migration from c++. If default is changed to false, it's very difficult to determine whether foremost widget is crypto or not in the NTP webui.
simonhong
added a commit
to brave/brave-core
that referenced
this issue
Nov 25, 2021
* Migrate crypto widgets visibility in NTP fix brave/brave-browser#19708 Migration is done once in the first NTP loading. For new users, all crypto widgets are hidden by default. For existing users, if current foremost widget is crypto widget, only it is visible and others are hidden. And, authed widgets are visible regardless of its position in widget stack After migration, user can control crypto widget's visibility from gallery. To make all crypto widgets hidden by default, each pref's default value is not changed. Their default prefs is still "true". As their visibility are managed by prefs and widget order is managed in local storage, it's difficult to start migration from c++. If default is changed to false, it's very difficult to determine whether foremost widget is crypto or not in the NTP webui.
7 tasks
rebron
changed the title
Hide crypto widgets by default on desktop
Update default widget list for desktop
Nov 29, 2021
LaurenWags
added
OS/Android
Fixes related to Android browser functionality
QA/Test-All-Platforms
feature/widgets
labels
Nov 29, 2021
Added labels that were on #19478 (duplicate issue) |
Removing Android label as there is an Android specific issue #19546 |
Verification passed on
Verification passed on
Verification passed on
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
feature/widgets
OS/Desktop
priority/P3
The next thing for us to work on. It'll ride the trains.
QA Pass-Linux
QA Pass-macOS
QA Pass-Win64
QA/Test-All-Platforms
QA/Yes
release-notes/include
This is desktop part of #19478
The text was updated successfully, but these errors were encountered: