I have configured this as next:
Also I leave untouched this:
When I press left mouse button on the link and move mouse up/down the page is scrolled up/down
instead of expected open the link in new foreground/background tab
It seems you do not distinguish two cases:
Despite on you mention that this action is on selected link
Opens either a selected link, ...
actually, you can not assign two or more actions to a gesture
it should be one to one
i guess that removing the assignment of "scroll to top/bottom" can solve your problem
I can. My recent gestures work in this way. Why your gestures can not do the same? I think this is not hard to distinguish those two specified cases.
There are too many problems with this concept, even though I would like to implement it. Just to name two of them: action priority (which action should run if both actions are possible), action success detection (for a lot of actions it's unsure if they will succed or not / if they succeded or not)
@Robbendebiene imho for this case the priority is clear, as the link is more specific than a general page-action.
Hi, I'd really like to see this implemented.
@KOTRET describes what was the logic in FireGestures and even in all the implementation that inspired these tools, running back to the first versions of Opera Browsers.
I can't comment on the "action success detection" but I agree that yeah, if you are on a specific element (url, image, whatever_you_want_to_support) that takes the precedence over other actions.
Since this has too many problems I'm closing this. Those who are interested in hybrid gestures can look here: https://github.com/Robbendebiene/Gesturefy/issues/313
Most helpful comment
actually, you can not assign two or more actions to a gesture
it should be one to one
i guess that removing the assignment of "scroll to top/bottom" can solve your problem