| 2014-06-05 20:44:36 |
Nicholas Skaggs |
bug |
|
|
added bug |
| 2014-06-05 20:45:22 |
Nicholas Skaggs |
description |
Simply put, if you push a new page as part of an ontriggered event for a toolbar button, and a that button is part of a popover, the next event on the pushed page is eaten by the popover which fails to close.
A simple example can be seen here:
lp:~nskaggs/+junk/pagestack-push
Run the included example.qml file and click the toobar button entitled 'Click Me!'. Notice the first click event to the textfield doesn't transfer focus as it should.
Including Tim's running commentary while investigating for more info :-)
<t1mp> the popover that shows the two actions doesn't close properly after the new page is pushed
<t1mp> so that is eating the events.
<t1mp> if I remove the pageStack.push from the action, it does close the popover
<t1mp> it seems it all works fine, except if in onTriggered, there is a pageStack.push().. then the Popover.close() that is called in onTriggered for the listitem (which represents the action) is not executed
<t1mp> when pushing a new page, the list of actions in the header changes, which destroys the list items in the popover that shows the actions
<t1mp> ^ and that happens before the onTriggered of the list item which should close the popover is executed
<t1mp> that messes up things |
Simply put, if you push a new page as part of an ontriggered event for a toolbar button, and that button is part of a popover, the next event on the pushed page is eaten by the popover which fails to close.
A simple example can be seen here:
lp:~nskaggs/+junk/pagestack-push
Run the included example.qml file and click the toobar button entitled 'Click Me!'. Notice the first click event to the textfield doesn't transfer focus as it should.
Including Tim's running commentary while investigating for more info :-)
<t1mp> the popover that shows the two actions doesn't close properly after the new page is pushed
<t1mp> so that is eating the events.
<t1mp> if I remove the pageStack.push from the action, it does close the popover
<t1mp> it seems it all works fine, except if in onTriggered, there is a pageStack.push().. then the Popover.close() that is called in onTriggered for the listitem (which represents the action) is not executed
<t1mp> when pushing a new page, the list of actions in the header changes, which destroys the list items in the popover that shows the actions
<t1mp> ^ and that happens before the onTriggered of the list item which should close the popover is executed
<t1mp> that messes up things |
|
| 2014-06-05 20:47:08 |
Tim Peeters |
ubuntu-ui-toolkit: assignee |
|
Tim Peeters (tpeeters) |
|
| 2014-06-05 20:47:07 |
Launchpad Janitor |
branch linked |
|
lp:~tpeeters/ubuntu-ui-toolkit/closeActionsPopover |
|
| 2014-06-05 20:47:11 |
Tim Peeters |
ubuntu-ui-toolkit: status |
New |
Confirmed |
|
| 2014-06-05 20:47:13 |
Tim Peeters |
ubuntu-ui-toolkit: importance |
Undecided |
Critical |
|
| 2014-06-05 21:43:51 |
Tim Peeters |
summary |
New header toolbar popover eats events |
PageStack.push() eats header action overflow event |
|
| 2014-06-05 21:44:44 |
Tim Peeters |
summary |
PageStack.push() eats header action overflow event |
PageStack.push() eats header action popover close |
|
| 2014-06-05 22:02:34 |
Tim Peeters |
ubuntu-ui-toolkit: status |
Confirmed |
In Progress |
|
| 2014-06-10 16:46:47 |
PS Jenkins bot |
ubuntu-ui-toolkit: status |
In Progress |
Fix Committed |
|
| 2014-07-11 13:24:08 |
Tim Peeters |
ubuntu-ui-toolkit: status |
Fix Committed |
Fix Released |
|
| 2014-10-01 12:03:15 |
Zoltan Balogh |
ubuntu-ui-toolkit (Ubuntu): status |
New |
Incomplete |
|
| 2014-10-01 12:03:18 |
Zoltan Balogh |
ubuntu-ui-toolkit (Ubuntu): status |
Incomplete |
Fix Released |
|
