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

GENERATE_TREEVIEW=YES disables touch scrolling with Android 3.x (Origin: bugzilla #707389) #5283

Closed
doxygen opened this Issue Jul 2, 2018 · 0 comments

Comments

Projects
None yet
1 participant
@doxygen
Copy link
Owner

doxygen commented Jul 2, 2018

status RESOLVED severity major in component general for ---
Reported in version 1.8.5 on platform Other
Assigned to: Dimitri van Heesch

On 2013-09-03 13:40:02 +0000, Suzumizaki-Kimitaka wrote:

When documents are generated with GENERATE_TREEVIEW=YES,
touch moving(scrolling) are DISABLED on Android 3.x devices.

For example, see http://doxygen.org with any browser installed
on such devices.

The behavior is caused by the code at the end of src/resize.js as follows:

$(document).bind('touchmove',function(e){
try {
var target = e.target;
while (target) {
if ($(target).css('-webkit-overflow-scrolling')=='touch') return;
target = target.parentNode;
}
e.preventDefault();
} catch(err) {
e.preventDefault();
}
});

But is this code really required?
The code says "When user agent doesn't have '-webkit-overflow-scrolling' feature,
We always kill touch-scrooling event even how long the document is vertically and
holizontally."

I think we should kill the code above instead of the touch-scrolling event,
but is there any reason the code should alive?

Regards,
Suzumizaki-Kimitaka

On 2013-10-13 10:02:25 +0000, Dimitri van Heesch wrote:

Confirmed. Should be fixed in the next GIT update.

On 2013-12-24 18:59:26 +0000, Dimitri van Heesch wrote:

This bug was previously marked ASSIGNED, which means it should be fixed in
doxygen version 1.8.6. Please verify if this is indeed the case. Reopen the
bug if you think it is not fixed and please include any additional information
that you think can be relevant (preferrably in the form of a self-contained example).

On 2015-06-25 20:39:22 +0000, Chad Kennedy wrote:

I can confirm that this is definitely not fixed in my case. I see the behavior (not able to scroll) in the following environments:

  1. Samsung Galaxy S6 edge; latest Chrome browser
  2. Motorola Xyboard; latest Chrome browser
  3. Motorola Xyboard; built-in browser

In case 3, when I turn off JavaScript support, the problem goes away. This points strongly to Suzumizaki-Kimitaka's explanation still being in effect.

@doxygen doxygen closed this Jul 2, 2018

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.