[
https://issues.apache.org/jira/browse/CB-8463?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14359456#comment-14359456
]
Shazron Abdullah commented on CB-8463:
--------------------------------------
Ouch - that's embarrassing :) Probably pre-3.0 code that we never bothered to
update to pluginInitialize when 3.x rolled around.
What do you mean by "two-stage initialization"? Are you suggesting we still
keep support for initWithWebView somehow? I would think that moving to a major
version that would give us latitude to break this dependency especially since
it was never publicly documented. I'm not opposed to it, and it's not a hard
technical problem -- we could start a discussion on the ML regarding this for
sure.
Inspecting how the initialization works, the initWithWebView(Engine) is called
first, then pluginInitialize not soon after, so there won't be timing issues
related to this (hopefully).
For initWithWebViewEngine, I'm going to remove it from the public API and put
it in a private header instead, so there won't be this problem in the future.
> StatusBarPlugin Issue scrollView not found when using WKWebView
> ---------------------------------------------------------------
>
> Key: CB-8463
> URL: https://issues.apache.org/jira/browse/CB-8463
> Project: Apache Cordova
> Issue Type: Sub-task
> Components: Plugin Statusbar
> Environment: iOS 8
> Reporter: Holly Schinsky
> Assignee: Shazron Abdullah
>
> When using the WKWebView Plugin and the StatusBarPlugin together, the
> following error is received from the *CDVStatusBar.m* class:
> {code}
> CDVStatusBar.m:128:18: error:
> property 'scrollView' not found on object of type 'UIView *'
> self.webView.scrollView.scrollsToTop = NO;
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
