diff options
| author | michaeln@google.com <michaeln@google.com@0039d316-1c4b-4281-b951-d872f2087c98> | 2012-04-26 01:24:00 +0000 |
|---|---|---|
| committer | michaeln@google.com <michaeln@google.com@0039d316-1c4b-4281-b951-d872f2087c98> | 2012-04-26 01:24:00 +0000 |
| commit | 345ff2294048cf8e5d3854f2ac42ab8feea3d9fb (patch) | |
| tree | f9fbe36f9e77ef369720d781b2a41db27c2c9392 /content/browser | |
| parent | 95050bbe16fe8201d69b0c4b48cc2f48efe1d442 (diff) | |
| download | chromium_src-345ff2294048cf8e5d3854f2ac42ab8feea3d9fb.zip chromium_src-345ff2294048cf8e5d3854f2ac42ab8feea3d9fb.tar.gz chromium_src-345ff2294048cf8e5d3854f2ac42ab8feea3d9fb.tar.bz2 | |
Switch chrome and chromiumDRT over to using the new WebKit API for dispatching
events into webkit/webcore. This also includes informing DomStorageContext
EventObservers of session storage mutations too since we're switching to handling
them in the same way as local storage events.
Note: This is patch 2 of a multi-sided affair. The new event handling won't be fully
turned on until patch 3 on the webkit side. Here's patch 1...
https://bugs.webkit.org/show_bug.cgi?id=84387
BUG=94382
Review URL: https://chromiumcodereview.appspot.com/10201010
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@134037 0039d316-1c4b-4281-b951-d872f2087c98
Diffstat (limited to 'content/browser')
| -rw-r--r-- | content/browser/dom_storage/dom_storage_message_filter.cc | 1 |
1 files changed, 1 insertions, 0 deletions
diff --git a/content/browser/dom_storage/dom_storage_message_filter.cc b/content/browser/dom_storage/dom_storage_message_filter.cc index 8175123..15d19b3 100644 --- a/content/browser/dom_storage/dom_storage_message_filter.cc +++ b/content/browser/dom_storage/dom_storage_message_filter.cc @@ -245,5 +245,6 @@ void DOMStorageMessageFilter::SendDomStorageEvent( params.key = key; params.new_value = new_value; params.old_value = old_value; + params.namespace_id = area->namespace_id(); Send(new DOMStorageMsg_Event(params)); } |