We just updated the nightly build (1712 and later) with a wide range of fixes related to fast clicks, bringing up the keyboard on text input focus, scrolling, showing links/buttons as active, not firing off a click if a scroll happened, etc. We’ve been testing this build with the following scenarios: https://github.com/driftyco/ionic/blob/master/test/unit/angular/service/tap.unit.js#L4, but we would love to get more developers testing the updates.
There are multiple open issues this build is fixing, so if you find any issues please post a comment on the most related issue:
Once the issues within this commit are ironed out the plan is to release beta2 next.
@adam, another issue is when scrolling the item list, the item shows grey background color. This was fixed in fisrt beta version, but occurs now again. The background color should only shows when tap the item.
I tested it on Android 2.3.
The main issue for me was the obligation to double tap an input field to fire up the keyboard.
This is fixed BUT the application crashes a lot when playing with inputs.
Note that this did not happened with Beta 1 nor previous version
Here are the logcat’s logs http://pastebin.com/zYR1JXWY
If you have a text field at the bottom of a screen, when you click/tap to enter into that field, the keyboard initially covers it - which could be confusing for users (as they cant see what they are meant to be typing into)… When you start typing however, the view/screen does scroll up so you can see what you are typing.
Suggestion: If you have put focus to a text field, can you ensure that that particular text field is visible, before they start typing.
@Lagoonwish Thanks for testing out this build. What device and platform version are you testing on that you are unable to scroll when the target was an input? These devices are what we’ve been using.
As for the background color, it’ll stay gray for a few pixels while you scroll, but once you go over 6 pixels it should remove the gray background, and will also no allow a click to happen on touchend/mouseup. Are you receiving any javascript errors and did you update the CSS too?
@coen_warmer.pane does not have position:fixed on purpose, and adding it may cause a few issues with scrolling and view transitions and animations. So in your case you could probably just add the custom css, but for the framework that needs to work in all cases it might do more harm than good.
After using latest nigthly build, and now my button and font seems not smooth anymore, you can see in below animation gif, that show sign in button and menu in sidebar seems so weird
Agreed that this is an issue. I have text inputs low on the screen on a non-scrolling page. It previously worked as expected with the active text input scrolled up to be visible. Now it remains hidden until I type something.
We’re actively working on a branch which fixes text inpust that get covered by the keyboard. We’ve also build a cordova plugin which reports the keyboard height so that we’re able to adjust correctly.
@ghprod So the fonts are no longer smooth since changing your css to use the nightly build? So when you switch the css back to beta.1, it’s smooth again?
@Lagoonwish Would you be able to create a codepen to replicate the issue?
Thanks for testing out the nightly build and we’ll work to get it fixed up, thanks!
@adam
Previously i use nightly build too, to fix about tap/click issue, and i dont have backup for last nightly build before Ionic Package: nightly 1.0.0-beta.1-nightly-1717 (2014-04-18)
So i cant test it with older nightly, perhaps you still have previously nightly version?