On Wed Nov 05 2014 at 8:50:59 AM Michal Mocny <mmo...@chromium.org> wrote:
> Telling people to turn to [insert any project from the external community] > for [a feature we used to support but is now openly supported elsewhere] -- > sounds amazing to me. > > What happened to the goal of "eventually cease to exist"? > Yeah, but it actually has to work. We've been poly-filling broken browser features for years! > > On Wed, Nov 5, 2014 at 11:26 AM, Joe Bowser <bows...@gmail.com> wrote: > > > On Wed Nov 05 2014 at 8:21:03 AM Andrew Grieve <agri...@chromium.org> > > wrote: > > > > > Here's the ionic plugin: > > > > > https://github.com/driftyco/ionic-plugins-keyboard/blob/ > master/src/android/IonicKeyboard.java > > > > > > Uses a GlobalLayoutListener. the approach is described here: > > > > > http://stackoverflow.com/questions/2150078/how-to- > check-visibility-of-software-keyboard-in-android > > > > > > Why leave the code in core if we don't have to? I think the majority of > > > apps wouldn't need these events (even if you do, you can listen for > > resize > > > events to do the same kind of detection) > > > > > > > I think this will break more things than it'll fix. Does the Ionic > plugin > > support all the versions of Android that we currently support? Are we > > really going to tell people to go to Ionic for a feature that we once > > supported? Even if this is technically better, this seems like it's a > > support nightmare. > > > > > > > > > > On Wed, Nov 5, 2014 at 11:05 AM, Joe Bowser <bows...@gmail.com> wrote: > > > > > >> I disagree. We recently fixed this when we went back to adjustResize > > from > > >> adjustPan, and we should just file a bug about the behaviour on the > > Samsung > > >> Tablet. > > >> > > > > > > > > >
