[Webkit-unassigned] [Bug 47715] New: Web Inspector: move frontend settings to local storage
bugzilla-daemon at webkit.org
bugzilla-daemon at webkit.org
Fri Oct 15 02:25:16 PDT 2010
https://bugs.webkit.org/show_bug.cgi?id=47715
Summary: Web Inspector: move frontend settings to local storage
Product: WebKit
Version: 528+ (Nightly build)
Platform: All
OS/Version: All
Status: UNCONFIRMED
Severity: Normal
Priority: P2
Component: Web Inspector
AssignedTo: webkit-unassigned at lists.webkit.org
ReportedBy: podivilov at chromium.org
CC: timothy at apple.com, fishd at chromium.org, rik at webkit.org,
keishi at webkit.org, pmuellr at yahoo.com,
joepeck at webkit.org, pfeldman at chromium.org,
yurys at chromium.org, jorlow at chromium.org,
bweinstein at apple.com, apavlov at chromium.org,
loislo at chromium.org
We would like to enable access to local storage from Web Inspector. However, there are two problems:
1. privateBrowsingEnabled setting is true for web inspector pages (see WebInspectorClient.mm), this prevents web inspector from modifying local storage (see StorageAreaImpl::setItem). According to comment, this is done to keep inspector out of history.
This can be solved by introducing new setting "excludeFromHistory" and then using it instead of "privateBrowsingEnabled" in WebInspectorClient.
2. chrome registers "chrome:" schema as no access (see RenderThread::EnsureWebKitInitialized), this prevents web inspector from accessing the local storage.
We can add "allowLocalStorageAccess" setting like it's already done for "allowUniversalAccessFromFileURLs" (see Document::initSecurityContext). But I don't feel like it's a good solution.
Any thoughts?
--
Configure bugmail: https://bugs.webkit.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
More information about the webkit-unassigned
mailing list