Comment 13 for bug 1288876

The problem i snot there - that piece of code hasn't been changed since 5.0.2. InverseMouseArea is not even executing that code when topmostItem is set. When that property is set, the component installs a filter and grabs all the topmost events and handles them. Clipping however seemes it brought changes in event handling, so the filter registration had to happen in a completely different way. Beside, there was a bug in the event consumption, so when topmost events were set, mouse events occurred in the inactive area (the whole) were eaten, and not propagated at all. These were all caused by the event handling changes/fixes in Qt5.2.