Bug 60108 - [chromium] dom storage code should use the securityOrigin() for the content settings check, not the frame's url
Summary: [chromium] dom storage code should use the securityOrigin() for the content s...
Status: RESOLVED WONTFIX
Alias: None
Product: WebKit
Classification: Unclassified
Component: WebKit API (show other bugs)
Version: 528+ (Nightly build)
Hardware: PC OS X 10.5
: P2 Normal
Assignee: Nobody
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-05-03 18:52 PDT by John Abd-El-Malek
Modified: 2013-04-11 13:45 PDT (History)
3 users (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description John Abd-El-Malek 2011-05-03 18:52:16 PDT 
From the discussion of bug 60066, it was pointed out that the content settings code for dom storage uses the frame's url, when it should be using it's securityOrigin.  Note that this is for the user-created content settings policy.