Comment #9 on issue 131510 by
kal...@chromium.org: "Confirm changes"
Could you give more details on how to reproduce this bug?
- what machines have sync set up?
- which machine(s) saw the warning?
- which machine(s) didn't see the warning?
- has it happened since May?
I ask because I just had a go at reproducing this by
- setting up chromeos sync with a test account (canary v22)
- signing into chrome on ubuntu (v22)
I was operating under the assumption that stuff was getting synced from
chromeos onto ubuntu, triggering the warning; however it looks like we
don't actually sync OS-installed extensions anymore, so its moot.
Is this all correct?