Skip to content

Close icon of dialog doesn't work with $.mobile.defaultDialogTransition set to "none" #3351

Mowd opened this Issue Dec 29, 2011 · 2 comments

4 participants

Mowd commented Dec 29, 2011

Due to performance issue I set transition to none.
$.mobile.defaultPageTransition = "none";
$.mobile.defaultDialogTransition = "none";

And there's problem on my Android device 2.3.6 when I use close icon (X) to close the dialog, the dialog will close, but it will re-open again.
Sometimes it also happened on iOS device.
It's normal when I remove $.mobile.defaultDialogTransition = "none", but the transition effect is very laggy.


I am able to reproduce this on iOS5 with this code:

I had a similar issue in a web site I am making. It's because the close dialog uses the virtual mouse click "vclick" rather than the normal "click" event. Essentially your tap is being placed on the close button and the thing that opens the dialog at the same time.

The reason removing $.mobile.defaultDialogTransition = "none"; works is because the dialog doesn't immediately disappear.

Going to make a pull request switching the close button from using vclick to click.



I'm not seeing the pull request you referred to in IRC.


This looks like the delay issue from vclick. Have you any issue with switching over to click for this, with a comment as to why?

@imjoshdean imjoshdean pushed a commit to imjoshdean/jquery-mobile that referenced this issue Jan 17, 2012
Josh Dean Fix to #3351, dialogs reopening when attempting to close them 240505a
@gseguin gseguin closed this Jan 19, 2012
@sheebz sheebz added a commit that referenced this issue Feb 29, 2012
@sheebz sheebz Fixes commit #3351 - 87db1cf. This breaks any widget e.g. datebox whi…
…ch was firing vclick events to close dialog. In addition, jquery mobile enables fastclick (vclick) out of the box, see useFastClick, the documentation actually advises that disabling will break widgets.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Something went wrong with that request. Please try again.