Feature #11969

Revisit scrolling settings, Stretch edition

Added by intrigeri 2016-11-20 09:00:29 . Updated 2016-12-22 17:37:36 .

Status:
Resolved
Priority:
Normal
Assignee:
Category:
Hardware support
Target version:
Start date:
2016-11-20
Due date:
% Done:

100%

Feature Branch:
Type of work:
Discuss
Starter:
Affected tool:
Deliverable for:

Description

It seems that 3.0~alpha1 does natural scrolling by default, while we decided two years ago (Feature #7779) to not do that.

Our custom settings live in config/chroot_local-includes/etc/dconf/db/local.d/00_Tails_defaults, but the way we do it may be obsolete in feature/stretch, as these settings have moved from org/gnome/settings-daemon/peripherals/touchpad to org/gnome/desktop/peripherals/touchpad. Which suggests that on Stretch, GNOME now enables natural scrolling by default.

We should update our survey of what other OS’es do with more recent info + info about scrolling settings, and decide how we want Tails 3.0 to behave.

During our December monthly meeting [1] we discussed this and decided to rather drop our customisation (as most of the OS are doing natural scrolling now) and let GNOME+libinput do what they think is best, i.e. natural scrolling in most cases.

This way we keep reducing our delta with upstream.

[1]https://tails.boum.org/contribute/meetings/201612/


Subtasks


Related issues

Related to Tails - Feature #7779: Revisit default touchpad settings Resolved 2014-08-13
Related to Tails - Bug #11993: Tap-to-click is disabled on Stretch Resolved 2016-11-23

History

#1 Updated by intrigeri 2016-11-20 09:00:50

  • related to Feature #7779: Revisit default touchpad settings added

#2 Updated by intrigeri 2016-11-20 10:54:45

  • Status changed from Confirmed to In Progress
  • % Done changed from 0 to 10
  • Type of work changed from Research to Discuss

I get natural scrolling (on a laptop with a touchpad) by default in all recent OS’es I’ve tried (OSX, Fedora 24, Ubuntu 16.10), and that’s also what feature/stretch (that has no customization for these settings) gives me. So I propose we simply do like everyone else, and let GNOME + libinput do what they feel is best (which might depend on the hardware being used).

#3 Updated by intrigeri 2016-11-20 10:55:04

  • Assignee changed from intrigeri to sajolida
  • QA Check set to Info Needed

sajolida, what do you think?

#4 Updated by sajolida 2016-11-21 11:55:38

  • Assignee changed from sajolida to intrigeri
  • QA Check deleted (Info Needed)

Windows 10 seems to stick to the old way: http://www.windowscentral.com/how-reverse-scrolling-direction-windows-10 so it’s not yet “everyone else”. But I’m fine with following the default in GNOME and doing this kind of change for 3.0 seems like the right time (and not any new major version).

#5 Updated by intrigeri 2016-11-23 16:19:45

  • related to Bug #11993: Tap-to-click is disabled on Stretch added

#6 Updated by intrigeri 2016-12-09 09:00:46

  • % Done changed from 10 to 50
  • QA Check set to Ready for QA

We decided to use natural scrolling in 3.x. I expect emmapeel will add the rationale from our December meeting here. Next step is to double-check that our preferred settings are applied in current feature/stretch.

#7 Updated by intrigeri 2016-12-21 11:25:49

  • % Done changed from 50 to 60

Done in Git, needs to test.

#8 Updated by intrigeri 2016-12-21 15:44:03

  • Assignee changed from intrigeri to emmapeel
  • % Done changed from 60 to 90
  • QA Check changed from Ready for QA to Info Needed

Implemented, works fine. Reassigning to emmapeel so that she adds the rationale from our December meeting, that explains the decision we made, here.

#9 Updated by emmapeel 2016-12-22 11:13:57

  • Description updated
  • Assignee deleted (emmapeel)
  • QA Check changed from Info Needed to Ready for QA

Changed the description.

#10 Updated by intrigeri 2016-12-22 17:37:36

  • Status changed from In Progress to Resolved
  • % Done changed from 90 to 100
  • QA Check changed from Ready for QA to Pass

Thanks!