[IPAD] change page flicking in landscape #2474
Comments
Do you have a sample you can show us that exhibits this problem? I'm not seeing it when using: or http://jquerymobile.com/test/docs/pages/page-transitions.html |
Here is a sample : Beta 3 Beta 2 => page transition works fine To reproduce the issue, in landscape mode, swipe left twice or more to navigate in the presentation then swipe right and go back to the home page. then try again to swipe or use a navigation link on the page. It should start to flick during the transition. Another way to reproduce the issue is to start the presentation in portrait mode, navigate at least to another page then change the orientation to landscape and try to navigate using a swipe or a button. It should start to flick during the transition. |
Thanks for the A/B samples that will help tremendously. I'm assuming you accidentally closed the issue, so I'll go ahead and reopen. :-) |
The flashing is due to focus() being set on the actual page element when transitioning to pages with no .ui-title. This was introduced in beta 3 by this checkin: Perhaps we should be delaying the setting of focus until transitions are complete. |
Ok, the flashing isn't due to the actual focus() call, but instead, is related to the CSS outline property which is enabled when the element has focus. This seems to be the same flashing problem that occurs when transitioning with a text input focused. I'm able to stop the flashing with:
I need to figure out if outline is an inheritable property or not. |
Outline doesn't inherit. Go for it. On Sep 20, 2011, at 2:54 PM, Kin Blas wrote:
|
@jsblas I tested your fix. Perfect ! It works well now :) Nice work. Thanks |
@jblas - Lock 'n load. |
Fix landed on the HEAD: |
Tested on IPAD 1/ IOS 4.3.3. In my Ipad presentation, in landscape orientation only, after changing page once correctly, the transitions flicking. Every page changes are flicking with any Fx transitions. There is no problem in portrait mode.
If I switch back to the beta2 with the exact same code, I don't have this issue.
Hope it can help to improve the library.
The text was updated successfully, but these errors were encountered: