Use the same code to serialize app window state for the renderer
commit90e4d186e09e3f92d46fb4da8736407238e06d85
authortmdiep@chromium.org <tmdiep@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98>
Sun, 9 Feb 2014 23:06:04 +0000 (9 23:06 +0000)
committertmdiep@chromium.org <tmdiep@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98>
Sun, 9 Feb 2014 23:06:04 +0000 (9 23:06 +0000)
tree4e90c9f772055030cb14476a13017bd6713b9777
parent51abb7b9478834db11fc46241fbb2978d809f747
Use the same code to serialize app window state for the renderer

We send the properties of the app window to the renderer process at
window creation time and when the native app window state changes.
The code to serialize the state into a dictionary is duplicated
across two different locations. They should just use the same code.

BUG=None

Review URL: https://codereview.chromium.org/157133003

git-svn-id: svn://svn.chromium.org/chrome/trunk/src@250023 0039d316-1c4b-4281-b951-d872f2087c98
apps/app_window_contents.cc
apps/shell_window.cc
apps/shell_window.h
chrome/browser/extensions/api/app_window/app_window_api.cc