Deleting something from the history view breaks scrolling and the ability to click on some things

Bug #1671121 reported by Andrew Hayzen
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
ubuntu-ui-toolkit (Ubuntu)
New
Undecided
Unassigned
webbrowser-app (Ubuntu)
Confirmed
High
Unassigned

Bug Description

What happened:
1) Launch the webbrowser-app
2) Go to the history view
3) Scroll up/down and notice that the scrolling works
4) Right-click delete the first entry
5) Try to scroll up/down and notice that the scrolling doesn't work, notice you can't click on history entries, but you can select back in the header. Notice then you can't scroll the webviews or select any of the tabs.

What I expected to happen:
After step #4 for the scrolling/click focus to still function.

$ lsb_release -rd
Description: Ubuntu 16.04.2 LTS
Release: 16.04

Xenial + overlay

$ apt-cache policy webbrowser-app liboxideqt-qmlplugin
webbrowser-app:
  Installed: 0.23+16.04.20170125.1-0ubuntu1
  Candidate: 0.23+16.04.20170125.1-0ubuntu1
  Version table:
 *** 0.23+16.04.20170125.1-0ubuntu1 500
        500 http://ppa.launchpad.net/ci-train-ppa-service/stable-phone-overlay/ubuntu xenial/main amd64 Packages
        100 /var/lib/dpkg/status
     0.23+16.04.20161028-0ubuntu2 500
        500 http://archive.ubuntu.com/ubuntu xenial-updates/main amd64 Packages
     0.23+16.04.20160413-0ubuntu1 500
        500 http://archive.ubuntu.com/ubuntu xenial/main amd64 Packages
liboxideqt-qmlplugin:
  Installed: 1.20.4-0ubuntu0.16.04.1+overlay1
  Candidate: 1.20.4-0ubuntu0.16.04.1+overlay1
  Version table:
 *** 1.20.4-0ubuntu0.16.04.1+overlay1 500
        500 http://ppa.launchpad.net/ci-train-ppa-service/stable-phone-overlay/ubuntu xenial/main amd64 Packages
        100 /var/lib/dpkg/status
     1.20.4-0ubuntu0.16.04.1 500
        500 http://archive.ubuntu.com/ubuntu xenial-updates/main amd64 Packages
        500 http://security.ubuntu.com/ubuntu xenial-security/main amd64 Packages
     1.13.6-0ubuntu1 500
        500 http://archive.ubuntu.com/ubuntu xenial/main amd64 Packages

Olivier Tilloy (osomon)
Changed in webbrowser-app (Ubuntu):
status: New → Confirmed
importance: Undecided → High
Revision history for this message
Olivier Tilloy (osomon) wrote :

This appears to be a UITK bug. I can easily reproduce with the attached standalone example on desktop. The list view can be scrolled using the mouse wheel, and items can be clicked. After right-clicking on an item and deleting it, scrolling the view with the mouse wheel doesn't work any longer, and clicking items does nothing.

Another interesting data point: when this happens in the history view in the browser, the "Done" button can still be clicked, which closes the history view. If I then press Ctrl+H to open the history view again, mouse navigation is still broken. So it's not just broken for the view, it's broken for the entire window (other windows are unaffected, this can be seen when opening two browser windows and opening the history view in each window).

Revision history for this message
Zsombor Egri (zsombi) wrote :

Let's try to rule out few things:
1) try to use the ListItem action to delete it
2) try to use a different delegate to delete the item.

Revision history for this message
Olivier Tilloy (osomon) wrote :

> 1) try to use the ListItem action to delete it

Deleting using the ListItem action doesn't trigger the issue.

> 2) try to use a different delegate to delete the item.

Deleting a different delegate from the action's onTriggered handler doesn't trigger the issue either.

So it looks like the problem has to do with using a popover in conjunction with deleting the caller? If I delay the removal of the item by one second (using a Timer), thus giving the popover time to be closed, then the issue is not triggered. Maybe the use of ListView.delayRemove would help?

Revision history for this message
Zsombor Egri (zsombi) wrote :

I explained 2) badly :) I was about to mean that use other component for delegate and put a button on it, so when you click it that button deletes the delegate. Just to rule out the ListItem itself. But the 1) already rules it out, so it is indeed the popover which does something bad. And probably it is related to the focus handling, as I do not see anything else the popover would affect the ListView functionalities.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Bug attachments

Remote bug watches

Bug watches keep track of this bug in other bug trackers.