Digital experiences for all disciplines
New Landing › How can we help? › Cardinal › mobile issues on Android
New Landing › How can we help? › Cardinal › mobile issues on Android
- This topic has 68 replies, 6 voices, and was last updated 9 years by
Rui Guerreiro – SUPPORT.
-
Posted in: Cardinal
-
September 30, 2014 at 7:29 pm #116074
Hi Swiftideas.
I have to add something here: I have a onepager with a scrollnavigation to a set of rows. With page transitions active the transition-animation is shown even when scrolling down to a row. The standard menu does not behave like this.
I also realize that the mobile-menu changes the url shown in the adress-bar – the standard-menu does not do this as well.
This is not Android-specific. Small sized desktop-browsers do this as well. Mac, Win, Android, whatever.
URL: http://bnbm.de/de/home-edit
Best regards.
Sascha
October 1, 2014 at 10:39 am #116287Hi @darthsaschi,
Can you open a new topic with this one because it’s different from this specific thread.
Also can you explain further about the transition animation. The url being display in the address bar is normal behavior when over a element.Great, will check the other issues.
Try to test in a different Android device if possible.-Rui
October 1, 2014 at 10:48 am #116294Ok.
October 1, 2014 at 10:58 am #116299thanks
October 6, 2014 at 2:31 pm #117620Hi Rui,
Will problem number 2 that you addressed in this thread be resolved in the next update?
Thanks.
October 6, 2014 at 2:59 pm #117629Can you try to change this code below, located in functions.js
mobileMenuHideTrigger: function() { body.addClass('mobile-menu-closing'); SWIFT.nav.hideMobileMenu(); SWIFT.nav.hideMobileCart(); },
to this one
mobileMenuHideTrigger: function(e) { e.preventDefault(); body.addClass('mobile-menu-closing'); SWIFT.nav.hideMobileMenu(); SWIFT.nav.hideMobileCart(); },
In this case is better to purge the cache after changing the code or even disable the W3 Total cache temporarily.
If this solution is consistent we should include it in a future update. At least in Chrome the behavior was ok.
Thanks
-Rui
October 7, 2014 at 9:14 am #117881Hi Rui,
Did some testing on this. Here were my findings. After changing the code as instructed, I tested the menu and cart slideout menus on all the major Android browsers (using a SGS4):
Opera: No problems
Firefox: No problems
Dolphin browser: Problem with the menu slideout (pops out slightly on close). Cart seems fine
Boat Browser: No problems
Chrome: No problemsSo a good result overall. Dolphin is a fairly popular browser on Android, so worth looking into that issue.
October 7, 2014 at 9:37 am #117896Hi,
Great result overall.
Yes Dolphin is getting more Popular everyday, the problem of Dolphin and other mobile browsers like the default Android browser is the lack of tools to debug.If we can’t inspect and debug things get really complicated and time consuming, also the behaviors change sometimes in different mobile devices with the same browser.
We will try to do our best.
Thanks.
-Rui
October 7, 2014 at 9:41 am #117900Ok thanks.
Will that updated code in functions.js be included in the 1.9 update?
October 7, 2014 at 9:50 am #117911I think it will, but have to confirm with Ed.
-RuiOctober 9, 2014 at 10:21 am #118815Hi Rui,
Only just noticed that after putting in your recommended code, it actually throws an Uncaught error. See attached screenshot…
Thanks.
Attachments:
You must be logged in to view attached files.October 9, 2014 at 10:31 am #118822Hi,
Check if the functions is declared exactly like this:
mobileMenuHideTrigger: function(e) {
With the “e” inside the parentesis
-Rui
October 9, 2014 at 10:33 am #118823Ignore my previous reply. I saw that is right in the attached screenshot.
The login details are still the same?-Rui
October 9, 2014 at 10:39 am #118825This reply has been marked as private.October 11, 2014 at 12:11 am #119404Can you try again. Seems fine now.
-Rui -
Posted in: Cardinal
You must be logged in and have valid license to reply to this topic.