-
Notifications
You must be signed in to change notification settings - Fork 972
Feat/enable threefinger swipe, closes #3299 #7786
Conversation
unsure why standard fails on travis but not locally, will fix soon, but of course PR feedback is welcome asap. |
@luixxiul the standard errors on travis are from code i did not even touch, is travis configured correctly? /home/travis/build/brave/browser-laptop/app/renderer/components/clipboardButton.js:40:1: Expected indentation of 8 space characters but found 0. |
@lucidNTR The travis error issue is known to the team and they are working on it lately. You do not have to be too worried on the issue. Please run test locally and if it is fine, then it is ok. |
Tagged as work in progress since ecd391c has caused some conflicts. |
3c06699
to
1d5138a
Compare
@liunkae i rebased my pr and also fixed a new issue where the system setting 'two AND three fingers' was not respected |
@lucidNTR Great! I'll review in a little while. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@liunkae are you sure you restarted brave between changing the settings? I looked at the code and i cannot find a way to explain the wrong behaviour you described. :-/ Maybe you just closed the window, not full quit? |
In one of my tests, I did not restart. Restarting seemed to fix the problem. Besides requiring a restart, the behavior now matches Firefox. In my opinion, we probably should either make a note somewhere that it requires a restart or find a way to not require a restart. |
i thought about this for a while, the problem is that preventing restarts requires checking either on every scroll, or polling the system settings, both seem overkill for a setting that 99% of users change twice in 4 years. a perfect place to show the info would be if braves setting had a checkbox to disable swipe navigation or enable. but currently i think it would be overengineering, maybe we can add a ticket to future?
- yes, all errors are my iPhone's fault
… Am 30.03.2017 um 18:37 schrieb Liunkae ***@***.***>:
In one of my tests, I did not restart. Restarting seemed to fix the problem. The behavior now matches Firefox.
In my opinion, we probably should either make a note somewhere that it requires a restart or find a way to not require a restart.
—
You are receiving this because you were assigned.
Reply to this email directly, view it on GitHub, or mute the thread.
|
Good points. Regardless, this PR is a step in the right direction. |
@darkdh is this one you could also review? 😄 |
Np |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Good job @lucidNTR.
js/components/main.js
Outdated
|
||
// isSwipeTrackingFromScrollEventsEnabled is only true if "two finger scroll to swipe" is enabled | ||
// the swipe gesture handler will only fire if the three finger swipe setting is on, so the complete off setting and three and two finger together is also taken care of | ||
if (systemPreferences.isSwipeTrackingFromScrollEventsEnabled()) { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Could you put this check in scroll-touch-begin
? Because we don't want user to restart for every system setting change. Other browsers do not require restart and we should have the same behavior.
Please squash all the commits after you make the change, thanks. |
1d5138a
to
6546acc
Compare
@darkdh Ok i tried my best to keep the impact as minimal as possible, yet check on touchstart. Let me know if there is still issues, but my feeling is this is mergeable now... |
argh i committed my yarn file. is this ok? i strongly think yarn is far supperiour and we should have this anyways, ok or should i remove? |
The PR which added yarn support was reverted once here: #6437 (comment) I don't think any progress is done so I think you should remove the file from this PR. |
What @luixxiul said. Please remove it thanks. |
6546acc
to
f217ff9
Compare
@darkdh ok removed, will look into that again at later point |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
�lgtm now thanks
Hi, I experience this bug with Brave version 0.18.29 on macOS 10.12.6
I have restarted brave after changing the setting. |
closes #3299
Test Plan: