Skip to content
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

Show object count next to each sync type #38798

Open
bsclifton opened this issue Jun 4, 2024 · 1 comment
Open

Show object count next to each sync type #38798

bsclifton opened this issue Jun 4, 2024 · 1 comment
Labels
feature/sync feature-request OS/Android Fixes related to Android browser functionality OS/Desktop OS/iOS Fixes related to iOS browser functionality

Comments

@bsclifton
Copy link
Member

Platforms

all

Description

Google can display the count for each object type for your sync chain if you visit https://chrome.google.com/sync. You can’t do anything with this information- but it does let you see the count.

Here’s how it looks:
image

We could potentially show this same type of data in Brave on brave://sync; specifically where the different types are toggled:
image

We could show the current counts to the right (how many on server, how many on client). If a limit is reached, we could show a red warning label, something like: “Error! Your history object count has exceeded the maximum allowed! Only your most recent history is synced” (or similar). This could be shown next to the type or at the top of the screen.

When the user sees these counts, they might want to then turn off that particular sync type. Especially if it's causing them to hit a limit.

@bsclifton bsclifton added feature/sync feature-request OS/Android Fixes related to Android browser functionality OS/Desktop OS/iOS Fixes related to iOS browser functionality labels Jun 4, 2024
@bsclifton
Copy link
Member Author

NOTE: this follow up is a longer term client-side fix for the server-side changes made in #35042

We can split this issue into platform separate issues when if we're ready to do this (have mock ups, it's prioritized, etc).

A follow up for this issue could be offering a way for the user to put in a request to delete all records for a given record type (ex: History). This would have let users who hit the bad state in #35042 get back into a good state. If the user was able to delete all history entries (what was taking up the quota), it could have got them back working again.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature/sync feature-request OS/Android Fixes related to Android browser functionality OS/Desktop OS/iOS Fixes related to iOS browser functionality
Projects
None yet
Development

No branches or pull requests

1 participant