Disabled item in QTreeWidget breaks navigation keys - bug or feature?

[Tannin]

Easy to reproduce: Create a new window, add a QTreeWidget with a couple of items then in the application code append a disabled item to the widget:

@QTreeWidgetItem *disabledItem = new QTreeWidgetItem(QStringList() << "last");
disabledItem->setDisabled(true);
ui->treeWidget->addTopLevelItem(disabledItem);@

Now the page-down and end buttons won't work on the widget, probably because the last item can't be selected.
The question is: Is this reasonable behaviour? Shouldn't the last enabled item be selected?

Is there a workaround for this?

[SGaist]

Hi,

Sounds indeed a bit strange. You should take a look at the "bug report system":http://bugreports.qt.io to see if someone already mentionned that behavior

[Tannin]

Well, I didn't find a fitting report so I created one myself: https://bugreports.qt.io/browse/QTBUG-44746