Bug 44482

Summary: [Qt] Expose API to enable/disable universal document access
Product: WebKit Reporter: Alex Karpenko <alexkarpenko>
Component: WebKit QtAssignee: Nobody <webkit-unassigned>
Status: RESOLVED DUPLICATE    
Severity: Normal CC: benjamin, tonikitoo
Priority: P2 Keywords: Qt
Version: 528+ (Nightly build)   
Hardware: All   
OS: All   
Bug Depends on:    
Bug Blocks: 31552    
Attachments:
Description Flags
This patch exposes an API for enabling/disabling universal access none

Alex Karpenko
Reported 2010-08-23 19:09:19 PDT
Created attachment 65204 [details] This patch exposes an API for enabling/disabling universal access The Qt API currently exposes a way to allow universal access from locally stored files. This is done by setting the QWebSettings::LocalContentCanAccessRemoteUrls attribute. In special circumstances it is desirable to enable universal access for both local and remote documents. WebKit allows universal access to be enabled by calling WebCore::Security::setWebSecurityEnabled(false). However, QWebSettings does not expose this in its API. This patch adds the QWebSettings::WebSecurityEnabled attribute to allow enabling/disabling universal access. By default universal access is disabled (QWebSettings::WebSecurityEnabled is false) as before, and can be enabled by the client by setting QWebSettings::WebSecurityEnabled to true.
Attachments
This patch exposes an API for enabling/disabling universal access (2.67 KB, patch)
2010-08-23 19:09 PDT, Alex Karpenko
no flags
Alex Karpenko
Comment 1 2010-08-23 19:27:17 PDT
Just noticed, that "true" and "false" should be swapped in the last sentence.
Ariya Hidayat
Comment 2 2010-08-23 21:46:00 PDT
Comment on attachment 65204 [details] This patch exposes an API for enabling/disabling universal access Following http://trac.webkit.org/wiki/QtWebKitAPI, please post a message first to webkit-qt mailing list. Clearing the review flag until we have some discussions.
Benjamin Poulain
Comment 3 2010-11-12 06:54:17 PST
*** This bug has been marked as a duplicate of bug 45436 ***
Note You need to log in before you can comment on or make changes to this bug.