After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 707389 - GENERATE_TREEVIEW=YES disables touch scrolling with Android 3.x
GENERATE_TREEVIEW=YES disables touch scrolling with Android 3.x
Status: RESOLVED FIXED
Product: doxygen
Classification: Other
Component: general
1.8.5
Other other
: Normal major
: ---
Assigned To: Dimitri van Heesch
Dimitri van Heesch
Depends on:
Blocks:
 
 
Reported: 2013-09-03 13:40 UTC by Suzumizaki-Kimitaka
Modified: 2015-06-25 20:39 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Suzumizaki-Kimitaka 2013-09-03 13:40:02 UTC
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
Comment 1 Dimitri van Heesch 2013-10-13 10:02:25 UTC
Confirmed. Should be fixed in the next GIT update.
Comment 2 Dimitri van Heesch 2013-12-24 18:59:26 UTC
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).
Comment 3 Chad Kennedy 2015-06-25 20:39:22 UTC
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.