Page receives display:none after samePageTransition #4078
Comments
Do you have transitions off on these pages? We note that turning this on can cause CSS issues with transitions so you need to handle that on your end.
|
I am using a transition. Is there a list of transitions that support allowSamePageTransition? If I'm not using a transition I might as well just re-render the template. |
@MauriceG - Mind setting up some tests to see which transitions work well with allowSamePageTransition, then helping us add those details to the docs? |
@toddparker sorry for delay. |
I'm quite sure I've been using 'slide'. |
@storm Juut ;-) |
See also #4612 (closed as duplicate) about this also happening with transitions other than "slide". |
See also the information provided in the thread of #3968 (closed as duplicate). |
Issue #4687 has been closed as duplicate. The ticket has a test page and that shows an issue with allowSamePageTransition whithout transition "slide". |
I ran into the same issue, calling changePage to same pageId (hash, transition slide, samePageTransition true) results in a blank page. As stated above, the active page class is removed. Since this issue already provides a test case like mine, I simply add my comment here. If you check issue #2529, this was already fixed with a simple if check in a previous version of JQM (commit: ca9df11). Looking at the code, which removes the activePageClass in JQM 1.3.1, this is called via transitionHandler -> doneIn() -> cleanFrom(). I've added the same if statement from issue #2529 to the function doneIn(), and the blank page is not shown anymore. Maybe I'm missing something, since I'm not really into JQM. But I hope this helps to find/fix the blank page issue.
var createHandler = function (sequential) {
...
doneIn = function() {
if ( !sequential ) {
// if ( $from ) { // replace line 3735 with
if ( $from && $from[0] !== $to[0] ) { // check from issue #2529
cleanFrom();
}
}
|
Same here. It has not been fixed yet so I am using these lines on my event handlers:
|
'Cannot call method '_trigger' of undefined' is fixed in 1.4.0, However, after upgrading from 1.3.2, $(this).addClass('ui-page-active'); hack does not work. Any workaround? |
7883326 in branch "issue-4078" should fix the issue with the active page class. However, we have to look into this issue #6382 (comment). |
@arschmitz - Is this commit 7883326 in branch "issue-4078" no longer needed? |
need to see why new page is not being pulled on same page transition |
…an check this and not remove page if true Fixes #4078 - Page receives display:none after samePageTransition
…e page transition Fixes #4078 - Page receives display:none after samePageTransition
…an check this and not remove page if true Fixes #4078 - Page receives display:none after samePageTransition
A transition from #mypage to #mypage (with allowSamePageTransition set to 'true') will set #mypage's css 'display' to 'none' after the transition is completed.
The text was updated successfully, but these errors were encountered: