I found this bug because 0.7.7 changes:- Modified: Refactor Window::onParentSized to not abuse Window::setArea_impl.- Modified: refactor some Window implementation: mostly breaking up setArea_impl, and then reducing some code repetition elsewhere.

I also have this problem, would like to try to solve it or find a work around...

I find that it affects many but not all ItemListbox's in my project. Mainly those using a custom item entry type.

The first item is always invisible, but it will appear if the ItemListbox is perturbed in a way that causes the content pane to be laid out again -- if the scrollbar is touched, or if the frame containing the item listbox is resized.