Sync: Display non-severe errors on about:sync in gray color rather than red.

components/sync_driver/failed_data_types_handler.cc

Index: components/sync_driver/failed_data_types_handler.cc
diff --git a/components/sync_driver/failed_data_types_handler.cc b/components/sync_driver/failed_data_types_handler.cc
index 790684447ab79cdbfbe036b086f637696d5ef156..058482dd317c17b98fe5ca481dd994e22b0aa8d6 100644
--- a/components/sync_driver/failed_data_types_handler.cc
+++ b/components/sync_driver/failed_data_types_handler.cc
@@ -45,6 +45,7 @@ bool FailedDataTypesHandler::UpdateFailedDataTypes(const TypeErrorMap& errors) {
         unrecoverable_errors_.insert(*iter);
         break;
       case syncer::SyncError::DATATYPE_ERROR:
+      case syncer::SyncError::DATATYPE_POLICY_ERROR:

[Nicolas Zea, 2014/07/14 17:36:02]

What purpose does DATATYPE_POLICY_ERROR have? It doesn't seem to do anything
different than DATATYPE_ERROR?

[stanisc, 2014/07/15 16:10:00]

Other than different severity and the way it is logged / displayed in UI it is
pretty much the same as DATATYPE_ERROR. I thought about adding a severity
separate from error type to SyncError but at the end decided it would be easier
to just derive severity from the error type. If you think it is a better idea to
separate severity and have to pass it to SyncError constructor, I could do that.
To minimize the code churn we could default to the LOG_ERROR severity and have
an overloaded constructor for the cases when we need to specify severity other
than LOG_ERROR.

         data_type_errors_.insert(*iter);
         break;
       case syncer::SyncError::CRYPTO_ERROR: