Bug 98121

Summary: [EFL][WK2] Add setting to allow file access from file:// URLs
Product: WebKit Reporter: Chris Dumez <cdumez>
Component: WebKit EFLAssignee: Chris Dumez <cdumez>
Status: RESOLVED FIXED    
Severity: Normal CC: d-r, gyuyoung.kim, hausmann, kenneth, laszlo.gombos, lucas.de.marchi, rakuco, ryuan.choi, tonikitoo, webkit.review.bot
Priority: P2    
Version: 528+ (Nightly build)   
Hardware: Unspecified   
OS: Unspecified   
Attachments:
Description Flags
Patch
none
Patch
none
Patch none

Chris Dumez
Reported 2012-10-02 00:01:45 PDT
We should add a setting to Ewk_Settings to that the browser can allow file access from file:// URLs. Such access is currently disallowed by default and makes testing with Minibrowser more complicated.
Attachments
Patch (5.79 KB, patch)
2012-10-02 00:11 PDT, Chris Dumez
no flags
Patch (5.79 KB, patch)
2012-10-02 01:22 PDT, Chris Dumez
no flags
Patch (7.63 KB, patch)
2012-10-02 04:24 PDT, Chris Dumez
no flags
Chris Dumez
Comment 1 2012-10-02 00:11:16 PDT
Chris Dumez
Comment 2 2012-10-02 01:22:08 PDT
Created attachment 166639 [details] Patch Fix bug title (add WK2 tag).
Raphael Kubo da Costa (:rakuco)
Comment 3 2012-10-02 03:50:17 PDT
Comment on attachment 166639 [details] Patch Looks fine to me. I wonder if it is possible to check that actually accessing local URIs works/does not work in the API tests?
Chris Dumez
Comment 4 2012-10-02 04:15:29 PDT
Comment on attachment 166639 [details] Patch Will take rakuco's feedback into consideration.
Chris Dumez
Comment 5 2012-10-02 04:24:58 PDT
Created attachment 166660 [details] Patch Take rakuco's feedback into consideration.
Raphael Kubo da Costa (:rakuco)
Comment 6 2012-10-02 04:30:10 PDT
Comment on attachment 166660 [details] Patch LGTM.
Dominik Röttsches (drott)
Comment 7 2012-10-02 05:10:49 PDT
Comment on attachment 166660 [details] Patch View in context: https://bugs.webkit.org/attachment.cgi?id=166660&action=review > Source/WebKit2/UIProcess/API/efl/tests/resources/local_file_access.html:16 > + document.title = "Frame NOT loaded"; I don't know the exact semantics of waitUntilTitleChangedTo() - is this document.title line needed? > Source/WebKit2/UIProcess/API/efl/tests/resources/local_file_access.html:24 > + setTimeout("checkFrameLoaded()", 300); Could you get rid of the timeout by using a callback to parent from the loaded iframe?
Chris Dumez
Comment 8 2012-10-02 05:14:59 PDT
Comment on attachment 166660 [details] Patch View in context: https://bugs.webkit.org/attachment.cgi?id=166660&action=review >> Source/WebKit2/UIProcess/API/efl/tests/resources/local_file_access.html:16 >> + document.title = "Frame NOT loaded"; > > I don't know the exact semantics of waitUntilTitleChangedTo() - is this document.title line needed? Well, yes, it is needed. The unit tests are testing both cases (local frame is loaded, and local frame is NOT loaded). Therefore, I also need to specific title when the iframe is not loaded. >> Source/WebKit2/UIProcess/API/efl/tests/resources/local_file_access.html:24 >> + setTimeout("checkFrameLoaded()", 300); > > Could you get rid of the timeout by using a callback to parent from the loaded iframe? What if the iframe is not loaded? (which happens when we disallow local file access from file:// URLs).
Dominik Röttsches (drott)
Comment 9 2012-10-02 05:57:57 PDT
(In reply to comment #8) > What if the iframe is not loaded? (which happens when we disallow local file access from file:// URLs). Yes, as discussed offline, it looks like then there wouldn't be a good way to detect the failure case without a timeout, in which case it's much easier to just have one timer for both cases. So, I am fine with leaving the timer there if there's no good way for both, success and load failure case.
Laszlo Gombos
Comment 10 2012-10-04 08:23:45 PDT
Comment on attachment 166660 [details] Patch Looks good to me, r+.
WebKit Review Bot
Comment 11 2012-10-04 08:52:20 PDT
Comment on attachment 166660 [details] Patch Clearing flags on attachment: 166660 Committed r130395: <http://trac.webkit.org/changeset/130395>
WebKit Review Bot
Comment 12 2012-10-04 08:52:25 PDT
All reviewed patches have been landed. Closing bug.
Note You need to log in before you can comment on or make changes to this bug.