Hi Don, No, it's a startup setting only right now. I'll look at the scrollview stuff when I have the chance.
Issue: https://issues.apache.org/jira/browse/CB-2384 On Wed, Mar 13, 2013 at 2:58 PM, Don Coleman <[email protected]> wrote: > Shazron, > > Did you get this to work? > > I think the scrolling fix removed the blank space (of tool bar height) that > was visible when scrolling to the bottom of the page. > > Are you adding an API to enable and disabled the accessory bar too? I > created the plugin for an app where we remove the toolbar on a page with > one field, but re-enable it on long forms. > > - Don > > > > On Mon, Mar 11, 2013 at 12:43 AM, Shazron <[email protected]> wrote: > > > Looking at Don's code, the main difference is the accessory view was > > removed from the superview, while I only hid it. Removing it from the > > superview fixes the problem that Andrew reported. > > > > The scrollview fix is something different - the fix alleges that with the > > accessory bar gone, the textfield being edited is too far "up" so we need > > to adjust for its position to be closer to the keyboard by expanding the > > scrollview size (I think). > > > > > > On Sat, Mar 9, 2013 at 7:50 PM, Shazron <[email protected]> wrote: > > > > > Thanks Don, not sure I understand how the scrollview fix works, I'll > take > > > look Monday. Pull request welcome as well ... > > > > > > > > > On Saturday, March 9, 2013, Don Coleman wrote: > > > > > >> Check out https://github.com/don/KeyboardToolbarRemover > > >> > > >> I think it has the code you need. > > >> On Mar 9, 2013 9:22 PM, "Shazron" <[email protected]> wrote: > > >> > > >> > Hmm the fix will be more gnarly than expected. I think the parent > view > > >> for > > >> > the accessory bar has to be resized as well to shrink it, it is > still > > >> > getting touches. I'll get to this Monday. > > >> > > > >> > > > >> > On Sat, Mar 9, 2013 at 7:18 AM, Andrew Grieve <[email protected]> > > >> wrote: > > >> > > > >> > > I remembered what the problem is with it. Where the accessory used > > to > > >> be > > >> > > is dead to touches. Try in mobile spec on the audio page. Bring up > > the > > >> > > keyboard and then try to tap on a button where the accessory would > > >> have > > >> > > covered. > > >> > > > > >> > > > >> > > > > > >
