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

2.16.2 : Since upgrade mobile version usability drops #10376

Closed
Glisse1 opened this issue Aug 4, 2016 · 8 comments
Closed

2.16.2 : Since upgrade mobile version usability drops #10376

Glisse1 opened this issue Aug 4, 2016 · 8 comments
Labels
answered For when a question was asked and we referred to forum or answered it. Bug For errors / faults / flaws / inconsistencies etc. Regression Indicates a feature used to work in a certain way but it no longer does even though it should.

Comments

@Glisse1
Copy link

Glisse1 commented Aug 4, 2016

Since upgrade from version 2.16.1 to 2.16.2 checking piwik from my phone became a hassle due to two reason:

  • scrolling is a hit-miss situation, often the widget are moved.. this is not good usability, in order to move a widget there should be something like long-press for 2 seconds, or i dont know.. but not the normal scrolling down.
  • widgets buttons (close, refresh, etc) are almost impossible to invoke.. there are widgets which i want to manually refresh.. right now this became impossible, i need to refresh the whole piwik in browser in order to get new data.. either make the buttons always visible (best solution, this is not a desktop that would maybe appreciate a fancy fade-in buttons on-mouse-over, just make the buttons always visible).. or make them appear on-click upon widget`s top bar, like it used to be in version 2.16.1.. now, the new move "feature" i believe disabled that

PS: No, the dedicated piwik app is not a solution for me because i want the customized install loaded on my phone, with all my modifications.. from the modified definition of last "24 hours" (i preffer google s way of resetting stats at midnight unlike piwik continuum) to all colors and icons for each site`s page, etc, etc..

@tsteur
Copy link
Member

tsteur commented Aug 7, 2016

I mentioned similar here: #10045 (comment) and I think it's due to that PR as otherwise not much has changed. Maybe it's worth reverting that patch again

@tsteur tsteur added the c: Usability For issues that let users achieve a defined goal more effectively or efficiently. label Aug 9, 2016
@tsteur tsteur added this to the 2.16.3 milestone Aug 9, 2016
@dev-101
Copy link

dev-101 commented Aug 15, 2016

I have the same problem with scroll since the last update (Chrome, Android), and looking at the changelog TouchPunch lib introduction is the cause of the accidental widgets movements.

I see 2 ways to fix this issue:

  1. Increase the minimum initial touch&hold event duration (for example , to 1,5 ~ 2 seconds), which should eliminate false or unintentional drags.

  2. As Piwik knows I am on mobile, we could add an option in settings to disable this lib.

Thanks

@mattab
Copy link
Member

mattab commented Aug 16, 2016

it should be good enough to fix this issue in Piwik 3.0.0 only as it is not critical

@mattab mattab modified the milestones: 3.0.0, 2.16.3 Aug 16, 2016
@mattab mattab added Bug For errors / faults / flaws / inconsistencies etc. Regression Indicates a feature used to work in a certain way but it no longer does even though it should. and removed c: Usability For issues that let users achieve a defined goal more effectively or efficiently. labels Aug 16, 2016
@tsteur
Copy link
Member

tsteur commented Aug 16, 2016

It may be critical for some power users but reverting the other patch would mean creating segments doesn't work on mobile which may not be too bad

@dev-101
Copy link

dev-101 commented Aug 16, 2016

Quick & Dirty fix for users who wish to revert to the old way before the official solution in the update becomes available:

METHOD 1:

1.1 go to dir

/.../piwik/plugins/CoreHome/CoreHome.php

locate line 99 and add two slashes // in front of the line:

//$jsFiles[] = "libs/bower_components/jqueryui-touch-punch/jquery.ui.touch-punch.min.js";

1.2 go to dir

/.../piwik/tmp/

and remove all dirs (except .htaccess file)


METHOD 2:

2.1 go to dir

/.../piwik/libs/bower_components/jqueryui-touch-punch/jquery.ui.touch-punch.min.js

open jquery.ui.touch-punch.min.js file with Notepad/code editor and remove the entire content from it, then re-save

2.2 go to dir

/.../piwik/tmp/

and remove all dirs (except .htaccess file)

@dev-101
Copy link

dev-101 commented Nov 14, 2016

Hi, are there any plans to also fix this in 2.x branch? We're at 2.17.1 currently and this issue is still unresolved.

Also, instead of removing the lib, we can define touch delay, offset and distance values that should prevent accidental firing, but still work for those who/when/if need it.

Thanks

@mattab
Copy link
Member

mattab commented Dec 6, 2016

@dev-101 no it won't be fixed in 2.x

@mattab
Copy link
Member

mattab commented Dec 18, 2016

Hello if you still experience the issue in Piwik 3 please re-open or create a new issue 👍

@mattab mattab closed this as completed Dec 18, 2016
@mattab mattab added the answered For when a question was asked and we referred to forum or answered it. label Dec 18, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
answered For when a question was asked and we referred to forum or answered it. Bug For errors / faults / flaws / inconsistencies etc. Regression Indicates a feature used to work in a certain way but it no longer does even though it should.
Projects
None yet
Development

No branches or pull requests

4 participants