Purge in-memory localStorage areas if the # of areas exceeds the limit

content/browser/dom_storage/dom_storage_message_filter.cc

Index: content/browser/dom_storage/dom_storage_message_filter.cc
diff --git a/content/browser/dom_storage/dom_storage_message_filter.cc b/content/browser/dom_storage/dom_storage_message_filter.cc
index 9479cc9ae1e1e5c39a73d44eaa66db75b840ccbc..7580973cc73edd320a9a644a14e3f8f20ba6acef 100644
--- a/content/browser/dom_storage/dom_storage_message_filter.cc
+++ b/content/browser/dom_storage/dom_storage_message_filter.cc
@@ -125,6 +125,10 @@ void DOMStorageMessageFilter::OnSetItem(
   DCHECK_EQ(0, connection_dispatching_message_for_);
   base::AutoReset<int> auto_reset(&connection_dispatching_message_for_,
                             connection_id);
+  if (!context_->CanSetItem(host_.get(), connection_id, key, value)) {
+    Send(new DOMStorageMsg_AsyncOperationComplete(false));
+    return;
+  }

[Mike West, 2013/03/06 13:41:11]

This would likely be fairly easy to move to DomStorageHost, as michaeln
suggested on the other patch.

   NullableString16 not_used;
   bool success = host_->SetAreaItem(connection_id, key, value,
                                     page_url, &not_used);