Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

M2.1: Not scrollable picture on mobile / product page #5302

Closed
andidhouse opened this issue Jun 28, 2016 · 45 comments
Closed

M2.1: Not scrollable picture on mobile / product page #5302

andidhouse opened this issue Jun 28, 2016 · 45 comments
Labels
bug report Component: Catalog Issue: Ready for Work Gate 4. Acknowledged. Issue is added to backlog and ready for development

Comments

@andidhouse
Copy link

andidhouse commented Jun 28, 2016

Steps to reproduce

  1. Install Magento 2.1 via download
  2. install official sample data
  3. Go to a product page
  4. try to scroll down by hovering the picture

Expected result

  1. The site scrolls down also by touching the product picture

Actual result

  1. the product picture is not "scrollable" that means if you place your finger over the picture and try to scroll down nothing happens

bildschirmfoto 2016-06-28 um 08 56 04

This issue appeared on early magento2 versions and was fixed then. Now it is there again and it is important. I do not know if this issue just happens when no product picture is uploaded and placeholder is shown or if this happens also with a product picture uploaded.

Anyway - this needs to be fixes asap as this is a massiv blocker for users.

@andidhouse
Copy link
Author

I think this is really an important bug stopping users to shop mobile at all so it needs to be reviewed here pls.

@andidhouse
Copy link
Author

@ilol can you pls have a look on this. i think it is really important as it is a total conversion blocker for mobile users!

thanks!

@ilol
Copy link

ilol commented Jul 19, 2016

Thank you @andidhouse , registered to fix MAGETWO-55608

@veloraven veloraven added Issue: Ready for Work Gate 4. Acknowledged. Issue is added to backlog and ready for development bug report labels Jul 28, 2016
@gazoscalvertos
Copy link

Please fix this, its a major issue on our site as the image spans 100% width.

@apurv-anand
Copy link

+1
Hit my this issue as well. Does anyone know any workaround for now?

@Simpsonight
Copy link

Here is a workaround for this bug which solves the problem.
Replace the hole onMove(e) function in file magento2/lib/web/fotorama/fotorama.js, at Line 1418, with the following code snippet:

function onMove(e) {
            if ((e.touches && e.touches.length > 1)
                || (MS_POINTER && !e.isPrimary)
                || moveEventType !== e.type
                || !touchEnabledFLAG) {
                touchEnabledFLAG && onEnd();
                (options.onTouchEnd || noop)();
                return;
            }

            extendEvent(e);

            var xDiff = Math.abs(e._x - startEvent._x), // opt _x → _pageX
                yDiff = Math.abs(e._y - startEvent._y),
                xyDiff = xDiff - yDiff,
                xWin = (tail.go || tail.x || xyDiff >= 0) && !tail.noSwipe,
                yWin = xyDiff < 0;


            if (touchFLAG && !tail.checked) {
              if (touchEnabledFLAG = xWin) {
                stopEvent(e);
              }
            } else {
                stopEvent(e);
                (options.onMove || noop).call(el, e, {touch: touchFLAG});
            }

            if (!moved && Math.sqrt(Math.pow(xDiff, 2) + Math.pow(yDiff, 2)) > tolerance) {
                moved = true;
            }

            tail.checked = tail.checked || xWin || yWin;
        }

@ghost
Copy link

ghost commented Sep 6, 2016

Has this been fixed? This is a pretty big issue for mobile shoppers. The workaround does not seem to work on 2.1.1 rendering Magento pretty useless on a good number of mobile devices.

@ghost
Copy link

ghost commented Sep 7, 2016

If you take a look at the default luma and blank theme this bug doesn't seem to have an impact on them. It rears its head on custom themes and is very present on several live sites I have looked at running CE.

@andidhouse
Copy link
Author

3 month later without an official bugfix of a major bug... i really do not know what is going on on magento side...

@ghost
Copy link

ghost commented Sep 14, 2016

It's pretty obvious, CE is not in the future.

@ghost
Copy link

ghost commented Sep 14, 2016

@andimov @ilol any info on this bugfix?

@ilol
Copy link

ilol commented Sep 15, 2016

Development completed. So we are merging this into mainline and older versions.

@ghost
Copy link

ghost commented Sep 15, 2016

Thanks for responding, if your able to provide a date, when will we be able to utilize this, and how?

mmansoor-magento pushed a commit that referenced this issue Sep 20, 2016
Bug
MAGETWO-56699 [GITHUB] Paypal checkout not possible with products that have custom options #5938 - for mainline
MAGETWO-58290 [Github]Empty product option is added on each PUT request #5963
MAGETWO-58136 [Github] Shipping and billing address are not set if order placed with payment action Sale #6438
MAGETWO-55608 [GITHUB] M2.1: Not scrollable picture on mobile / product page #5302
MAGETWO-58285 Ajax error message doesn't display in backend
MAGETWO-58338 [Github]Problem adding attribute options that start with a number via REST Api #5715
MAGETWO-52575 Unable to apply free shipping to specified method when creating order in admin
MAGETWO-57078 [GITHUB] Can't set customer group when creating a new order in the admin. #6162
MAGETWO-58039 Table rate shipping not applying correctly - for mainline
@SerhiyShkolyarenko
Copy link
Contributor

Fix of MAGETWO-55608 is delivered to develop branch. Closing the issue.

@PaperDS
Copy link

PaperDS commented Oct 10, 2016

I have test site with v2.1.1 and am having the same problem with Luma and sample data installed.
Scroll not working on mobile. http://test.starfishratings.net/

@ghost
Copy link

ghost commented Oct 10, 2016

@PaperDS the fix is available in the developer branch, you could grab it from there and add it to your current install.

@keyurshah
Copy link

still seems to be an issue in the version released today, 2.1.2

@ghost
Copy link

ghost commented Oct 13, 2016

Yes, I can confirm the fix isn't in 2.1.2. Not sure why....

@PaperDS
Copy link

PaperDS commented Oct 13, 2016

So will this issue be reopened?

@jibrandlr
Copy link

jibrandlr commented Oct 13, 2016

@PaperDS Currently Magento 2.X.X has hundreds of issues. So far every release comes with fixes for 5-10 of those issues plus new ones of the specific release.
Some of the fixes are already available in the developer branch. That doesn't mean the fixes will be included in the next release. It might take Magento months (years?) to include those fixes in an "official" release.
You have 3 options:

  • Stay with Magento 1
  • Search for the fix of your issue in the developer branch
  • Drop Magento and choose a software that just works as expected

@ghost
Copy link

ghost commented Oct 13, 2016

Are there as many issues with EE?

@jibrandlr
Copy link

@jupiter01 I don't know really (i'm not a Magento employee). My previous comment is based on my experience so far using Magento 2 CE and the number of issues reported already in github by the community.

@sshymko
Copy link

sshymko commented Nov 16, 2016

Suffering from the same issue.

@piotrekkaminski @elenleonova @pboisvert
What release is the fix going to be included in? When is it coming out?

@erikhansen
Copy link
Contributor

erikhansen commented Nov 17, 2016

Applying the 7597a52 commit as a patch (add .patch to the end of that url to get a patch file) to my environment fixed the issue for me.

@yofisim
Copy link

yofisim commented Nov 23, 2016

After updating the following files, the patch is still not working.

@giusecapo
Copy link

Did anyone find a solution?

@yofisim
Copy link

yofisim commented Nov 24, 2016

Hi all, after some reviews, as I'm a very noobie to magento.
When I imported the files, the fix was not working for me too..
But after digging, I found that you have to recompile the files for the patch to work.
Which means you have to:

  1. Replace the fotorama files as explained in the thread.
    2 Run the following queries in M2 root folder in command line:
    php bin/magento setup:upgrade
    php bin/magento setup:di:compile
    php bin/magento setup:static-content:deploy
    php bin/magento cache:flush
    php bin/magento index:reindex

And this should work. At least it did for me!
Thumb up if it worked 👍 !

More info about M2 command line here: http://devdocs.magento.com/guides/v2.0/config-guide/cli/config-cli-subcommands.html

@giusecapo
Copy link

giusecapo commented Nov 24, 2016

Sorry, I'm noobie (a lot) too, how to install the patch? @yofisim

@yofisim
Copy link

yofisim commented Nov 24, 2016

You will find the files to replace (and the exact lines that have been changed) here:
7597a52

Replace them, then go for the few commands I gave you.

Good luck 💯

@giusecapo
Copy link

Unfortunately, I did everything exactly as you suggested me... But it still doesn't work :( @yofisim

@yofisim
Copy link

yofisim commented Nov 24, 2016

@giusecapo on your browser, when you're on the product page, check the fotorama.js file the browser process to see if you have inserted the correct files and did the right manipulation

@giusecapo
Copy link

You're right, page is loading fotorama.js from pub/static/... Do you know why? Should I clear static files again? @yofisim

@giusecapo
Copy link

Ok! It works! Thanks for your help, maybe I called deploy static content before ftp finished upload :) You made my day man @yofisim

@yofisim
Copy link

yofisim commented Nov 24, 2016

@giusecapo
Yes it's right, Magento needs this file to process the images and render them.
I want you to check the file itself, and see if the change you made is taken by the browser.

Report again to these files here: 7597a52

and check the changes @

@yofisim
Copy link

yofisim commented Nov 24, 2016

Ow nice! thumb up! Have a nice dev day @giusecapo

@jmtakahashi
Copy link

@ilol @yofisim note that this fix works on initial page load, but on reload (refresh) it does not work. on reload, first image in the slider will react to up and down scrolling, but on 2nd image or 3rd image (any image after first), the scrolling issue persists.

@yofisim
Copy link

yofisim commented Dec 5, 2016 via email

@jmtakahashi
Copy link

@yofisim

Device:
a.) iphone 6s
b.) private browsing mode

Magento 2.1.2 (i'm including these because the JS merge, minify and bundle are problems in themselves when set to on)
a.) Minify, Bundle, Merge JS: ALL OFF
b.) Merge and Minify CSS: ON
c.) Minify Html: OFF

1.) Click to an individual product page from any page.
2.) Check slider (all images), and check scrolling. It will work.
3.) Reload the individual product page a few times.
4.) Check slider (default first image), scrolling will work with first image.
5.) Slide to 2nd or 3rd image, scrolling up and down while finger is over the image stops working.

Hope this helps. I'm not sure whether the Private Browsing mode has anything to do with it, but reloading the page (today) once, and it still worked. Then the 2nd time reloading it stopped working again.

@yofisim
Copy link

yofisim commented Dec 6, 2016 via email

@jmtakahashi
Copy link

@yofisim this was tested on an actual phone. https://vizume.com

Any product image does the same thing.

@andidhouse
Copy link
Author

we give it up on the native photorama implementation due to:

  • problem with mobile devices and scrolling issue
  • extreme long load times of the script compared to for example magic zoom
  • some other small bugs and in general poor implementation of the script at this moment

Magic zoom works like a charm and has a great support fixing bugs in minute not years.

@elenleonova
Copy link

The issue has been delivered to 2.1.3

@andidhouse
Copy link
Author

i can confirm this is fixed n 2.1.3
thanks!

@erik-augustin
Copy link

Its not fixed on Chrome on ios iphone. Its fixed in Safari.

@through-a-haze
Copy link

@erik-augustin just rechecked. It's fixed on both for me.

magento-engcom-team pushed a commit that referenced this issue Feb 10, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug report Component: Catalog Issue: Ready for Work Gate 4. Acknowledged. Issue is added to backlog and ready for development
Projects
None yet
Development

No branches or pull requests