On Fri, Mar 22, 2013 at 1:01 PM, Andrew Grieve wrote:
> Could you call requestFocusFromTouch() on your other component after the
> WebView calls it?
>
I was going to ask the same question.
I also got frustrated with methods being protected or private but there are
usually ways around it.
Yeah, this was a concern for me as well, but I figured I'd wait and see
what the pull request looked like to know whether it would be a hard thing
to maintain.
- Could you call requestFocusFromTouch() on your other component after the
WebView calls it?
On Fri, Mar 22, 2013 at 2:50 PM, Joe Bowser
-1
I don't want anything public until we have a process to decide on what
we should or should not support. We've been burned in the past by
making certain things public, and then not being able to change those
methods because someone somewhere depends on it for their app.
Architectural flexibilit
I've messed around with programmatic view manipulation in native apps, on
droid and iOS primarily. There's no reason that I'm aware of that these
methods need to be private, and making sure that plugins/native code can
change the view layout is important for overall architecture flexibility.
It may
Sounds good to me!
On Thu, Mar 21, 2013 at 9:09 PM, wrote:
> Hi all,
>
>
>
> We have an android application mixing native views and a CordovaWebView.
> The problem is the CordovaWebView request the focus when launching the
> application even in our case it should not be the view selected by
> d
