Apply content-security-policy directive to chrome://workers page.

Apply content-security-policy directive to chrome://workers page.

The changes to chrome_web_ui_data_source allow for alternate message loops
and the absence of translated strings, which are cases I didn't think we'd
encounter.  But we did.
Committed: http://src.chromium.org/viewvc/chrome?view=rev&revision=98110

[Tom Sepez, 2011-08-23 19:07:47]

Found another one.  Please review.

[Evan Stade, 2011-08-24 20:47:23]

lgtm

http://codereview.chromium.org/7714007/diff/2002/chrome/browser/ui/webui/chro...
File chrome/browser/ui/webui/chrome_web_ui_data_source.cc (right):

http://codereview.chromium.org/7714007/diff/2002/chrome/browser/ui/webui/chro...
chrome/browser/ui/webui/chrome_web_ui_data_source.cc:55: if (!json_path_.empty()
&& path == json_path_) {
I think it would be perhaps clearer to instead do

DCHECK(!path.empty())

at the start of the function (I think that's equivalent).

[Tom Sepez, 2011-08-24 20:52:36]

http://codereview.chromium.org/7714007/diff/2002/chrome/browser/ui/webui/chro...
File chrome/browser/ui/webui/chrome_web_ui_data_source.cc (right):

http://codereview.chromium.org/7714007/diff/2002/chrome/browser/ui/webui/chro...
chrome/browser/ui/webui/chrome_web_ui_data_source.cc:55: if (!json_path_.empty()
&& path == json_path_) {
Not quite.  json_path_ can be empty if the particular source doesn't have any
json to return, and thus hasn't called set_json_path().  We don't want to take
this path unless the json_path has been set.