Moving through form in Mobile Safari with "Next" and "Previous" system controls causes fixed position, tap-toggle false Header to reveal itself #4724

Closed
ceslami opened this Issue Jul 19, 2012 · 1 comment

Projects

None yet

3 participants

@ceslami
ceslami commented Jul 19, 2012

When filling out a form in mobile Safari on iOS, the user has the option to progress to the next field by using system "Previous" and "Next" buttons on the keyboard. When using a JQuery mobile header with data-position="fixed" and data-tap-toggle="false", the header should never flash into view. However, when using these native form progress controls, the header flashes into view, before quickly flashing out of view.

Using:

iOS 5.1.1
Mobile Safari

@MauriceG
Contributor

I can confirm this issue on iPhone (not iPad) : http://jsfiddle.net/MauriceG/bqyhj/show/light/

With iPhone portrait:

  • scroll down to the last item in the form
  • tab into the "city" item
  • use the previous function on the system keyboard until you are in the "email" item
  • use next and previous alternately

Maurice

@arschmitz arschmitz added a commit to arschmitz/jquery-mobile that referenced this issue Oct 22, 2012
@arschmitz arschmitz FixedToolbar: add check to ensure toolbars are in the proper position…
… after scroll and repositioning logic. Fixed: #4337 - Fixed header problem after scrolling content on iOS and Android, #4113 - Header and footer change their position after keyboard popup - iOS, #4724 - Moving through form in Mobile Safari with "Next" and "Previous" system controls causes fixed position, tap-toggle false Header to reveal itself
3f5a5bb
@jaspermdegroot jaspermdegroot pushed a commit that closed this issue Nov 19, 2012
@arschmitz arschmitz FixedToolbars: Wait for stack to unwind before showing tollbars on fo…
…cusout to make sure we have not jumped to another input. Fixed #4724 - Moving through form in Mobile Safari with "Next" and "Previous" system controls causes fixed position, tap-toggle false Header to reveal itself
8d1a563
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment