textfields capture vertical swipes

[Leo Arias]

When you try to swipe a page vertically to make the bottom or top visible, if you start the swipe with your finger over a text field, nothing will happen.
This is confusing, as for a user there seems to be no good reason for the swipe to have failed. He might try it again starting from the same place with the same result. Then he might try to start the swipe from a different point, and it will work. It won't be clear that it failed only when the finger was over the textfield.
And as far as I understand, this shouldn't be the case. The textfield will always have a single line of text, so you will never need to do a vertical swipe inside the component. This is different from a TextArea that might have more than one line, and then a vertical swipe starting on the text area will result on a change inside the component, so the user will understand that he needs to swipe somewhere else to make a different part of the page visible.

[Leo Arias (elopio)]

<elopio> zsombi: so the question is: do text fields capture vertical swipes? and if so, why?
<zsombi> elopio: there is the Flickable inside the TextField, and that captures it :(
<elopio> zsombi: why is there a vertical flickable inside textfield, if it's never going to need vertical flicking? or is it that the flickable for horizontal swiping captures also the vertical movements?
<zsombi> elopio: checking if we can force Flickable to take only horizontal swip[es
<zsombi> elopio: unfortunately we cannot control that :(
<zsombi> elopio: and we need a horizontal swipe there...
-*- zsombi eod
<elopio> zsombi: I thought flickableDirection was for that.
<elopio> oh, you are gone. I will report a bug because this affects the UX. I find it weird that swipes don't work on text fields. I guess it will take some time to fix it though.
<zsombi> elopio: arghhhh!!! my eyes do not see anymore...
<elopio> zsombi: don't worry, go and get some rest :) This can wait until tomorrow.
<zsombi> elopio: that should do the job!
<zsombi> elopio: kewl...

[Leo Arias (elopio)]

This is making calendar tests fail. See bug #1370563.
I'm not sure if we should wait for this bug to be fixed, or apply a workaround on the calendar.
We will need to do something different for text areas, that also capture the vertical gesture. But I can't think of a way to know if we are starting the swipe over a text area. Or how to tell which is a save point to start swiping.

[Cris Dywan (kalikiana)]

Is this about not being able to swipe in parts of a text field where there is no text?

[Leo Arias (elopio)]

Also where there is text. Because if it's a single line, it doesn't make sense to capture up and down finger movements, I think. It doesn't matter if there is text or not.

[Launchpad Janitor (janitor)]

This bug was fixed in the package ubuntu-ui-toolkit - 1.3.1984+16.10.20160527.2

---------------
ubuntu-ui-toolkit (1.3.1984+16.10.20160527.2) yakkety; urgency=medium

  [ Christian Dywan ]
  * Slimmer frame for TextFields: 0.5dp. Fixes LP: #1578190.

  [ Albert Astals Cid ]
  * Add override
    The override specifier (since C++11) specifies that a virtual function
    overrides another virtual function. In a member function declaration or
    definition, override ensures that the function is virtual and is overriding
    a virtual function from the base class.

  [ Tim Peeters ]
  * Fix reference error in PullToRefreshStyle. Fixes LP: #1582843
  * Mark Tab, Tabs, TabBar, PageHeadConfiguration, PageHeadSections,
    PageHeadState, ToolbarButton, ToolbarItems as deprecated in the
    documentation. Fixes LP: #1566735, LP: #1566741.

  [ CI Train Bot ]
  * Resync trunk.

 -- Zoltan Balogh <email address hidden> Fri, 27 May 2016 07:08:44 +0000