+ewald

If we don't have the data counters today, I wouldn't consider them a launch blocker.

The code for the data counters should already exist. We display the counters in the user manager when you try to delete a profile: https://drive.google.com/a/google.com/file/d/0Byv8caX1Ib9dVWJXLVVkM0dVZDQ/view?usp=sharing.

I view this as a very-nice-to-have. Helps users who are deleting profiles understand the significance of the action they're taking. But if it's prohibitively expensive from an eng perspective, I think it's fine to remove the counts (we should still have the note about how to get your data back later).

We'll keep at P3 so it won't block launch, but will try to get it in before if possible.

Okay guys, thanks for the info!

This is in my queue. I will focus on the launch blocking stability issues for now.

This issue has been Available for over a year. If it's no longer important or seems unlikely to be fixed, please consider closing it out. If it is important, please re-triage the issue.

Sorry for the inconvenience if the bug really should have been left as Available. If you change it back, also remove the "Hotlist-Recharge-Cold" label.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

We recently made a pass at updating our "remove profile" UI, and we no longer show datatype counters when users are deleting a syncing profile, since the extra information doesn't provide much value to the user and is potentially overly-scary.

Closing this out for now.