Updates:
Summary: Invalid or non-canonical URL in a bookmark will cause sync
failures
Comment #1 on issue 19780 by [email protected]: Invalid or non-canonical URL
in a bookmark will cause sync failures
http://code.google.com/p/chromium/issues/detail?id=19780
[also http://b/1677563]
Chrome's bookmark model doesn't allow a bookmark to have an invalid URL
(specifically, BookmarkModel::AddURL will fail if !GURL::is_valid).
However, syncapi
accepts any string. Thus, an invalid URL entering the system (e.g. though
a script)
has the possibility of causing sync to unhinge.
At the very least, we could trigger SetUnrecoverableError here. Right now,
we crash.
ProfileSyncServiceTest.ServerChangeWithoutInvalidURL addresses this issue
but is
disabled until this bug is resolved.
--
You received this message because you are listed in the owner
or CC fields of this issue, or because you starred this issue.
You may adjust your issue notification preferences at:
http://code.google.com/hosting/settings
--~--~---------~--~----~------------~-------~--~----~
Automated mail from issue updates at http://crbug.com/
Subscription options: http://groups.google.com/group/chromium-bugs
-~----------~----~----~----~------~----~------~--~---
