You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cordova.apache.org by "Brent Allen (JIRA)" <ji...@apache.org> on 2016/03/26 00:09:25 UTC
[jira] [Comment Edited] (CB-10967) IndexedDB API not properly
exposed?
[ https://issues.apache.org/jira/browse/CB-10967?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15212565#comment-15212565 ]
Brent Allen edited comment on CB-10967 at 3/25/16 11:08 PM:
------------------------------------------------------------
To reproduce all that should be needed is a fresh app with the latest components Cordova@6+ and Cordova-iOS@4+.
Build it and inspect for the webkit/prefixed version of IndexDB api.
was (Author: ballen):
To reproduce all that should be needed is a fresh app with the latest components Cordova@6+ and Cordova-iOS@4+.
Build it and inspect for the webkit version of IndexDB api.
> IndexedDB API not properly exposed?
> -----------------------------------
>
> Key: CB-10967
> URL: https://issues.apache.org/jira/browse/CB-10967
> Project: Apache Cordova
> Issue Type: Bug
> Components: iOS
> Affects Versions: 4.0.0
> Environment: Cordova CLI 6.x.x, Cordova-iOS 4.x.x
> Reporter: Brent Allen
> Priority: Blocker
>
> So before cordova-ios 4.0.0 I was using https://github.com/Telerik-Verified-Plugins/WKWebView.git as a workaround to get the extra webkit apis/performance.
> Clearly not an ideal workaround since it requires a localhost origin. Making several CORS and iFrame operations a major headache.
> So I need to update to the latest frameworks. And I was successful in doing so with one catch.
> The webkit api for IndexDB is not exposed anymore. I am a little confused as to how this could be since it was expose when using the workaround. The only diff that I can find that seems to relate to webkit is this:
> From 'plugins/com.telerik.plugins.wkwebview/www/wkwebview.js'
> ```
> var origNativeFetchMessages = exec.nativeFetchMessages;
> exec.nativeFetchMessages = function() {
> var cmds = origNativeFetchMessages();
> cmds = JSON.parse(cmds);
> for(var i=0;i<cmds.length;i++) {
> var cmd = cmds[i];
> if(cmd[1]==='WKWebView') continue;
> window.webkit.messageHandlers.cordova.postMessage(cmd);
> }
> return '';
> };
> ```
> Which was also still available in cordova-ios@3.9.2(I think)
> I can't help but wonder if this has something to do with exposing the open versions of the api(s). And if so was this supposed to be re-implemented using the latest patterns?
> I am using mWater/minimongo which relies on this api. I already opened an issue on that repo. But I am not optimistic that it will be addressed there since the api hasn't technically changed as far as I can tell. It is just being hidden by the webview and the cordova platform is no longer exposing it manually.
> Any advice would be greatly appreciated. I am hoping to avoid cloning the minimongo repo. Since I am not even sure the apples implementation will work as I have yet to find any documentation on it.
> I am also concerned that this may have implications for other webkit apis that I have yet to discover as broken in this context.
> Thanks in advance for any help.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@cordova.apache.org
For additional commands, e-mail: issues-help@cordova.apache.org