Jump to content
thirty bees forum
  • 0

Datakick Critical Error on Mobile (big screen) - Checkout module (Chex)



We are using Chex module from @datakick in our online store, unfortunately we are encountering a very strange and serious problem, related to floating on mobile devices with larger screen. For example, this is seen in Samsung Galaxy Note 10+, which makes it virtually impossible to place an order on mobile. Important note: you won't see this on Chrome, only on mobile is it visible.

Interestingly, in a way it is random, because for many refreshes of the page it happens once or twice that such a problem does not occur, however, in the vast majority it is visible. For smaller screens, everything is fine.

Has anyone encountered this problem and possibly is able to suggest what it could be related to? I am attaching a screenshot showing the problem.

All the best!


Link to comment
Share on other sites

4 answers to this question

Recommended Posts

  • 0

@datakick thank you for your feedback. Maybe I was not precise enough - the problem affects not only strictly Samsung Galaxy Note 10 Plus, but all devices with larger screens, on the market currently quite a lot of this type, since problem is critical.

Disabling floating on mobile fixes the problem, but floating is a great feature, that looks good on the desktop, hence I'd rather avoid it.

The strangest thing in all this is that this problem is caused randomly - once it is, once it is not, more often it occurs, unfortunately. Do you have any more ideas?

Link to comment
Share on other sites

  • 0

The module contains js library to determine screen resolution, and use it to determine if the floating cart is supported or not. On small displays it's automatically disabled. I guess there is some bug in the library itself, or in the browser on the devices, that reports wrong screen size sometimes. The size detection seems to be working correctly when testing on desktop browser in mobile mode. 

It will be hard to fix, as debugging in mobile is very limited, ... and I don't have such device that is affected by this problem.

I could implement a feature that would force-disable cart floating on specific device(s), based navigator.userAgent browser property

Link to comment
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
  • Create New...