Thanks. Just to clarify, in beta 1, a list had its own height, based on the total height of the items. So if you turned off scrollability, you could have the list take up as much room as it needed, but no more. That's the behavior that I'm hoping to get back. I assume this was changed because of the infinite-scrolling feature, in which case you obviously can't know the total height of the items. But hopefully there's a way to tell it that you have a finite data store.

I've got a similar issue. I have a container followed by a list, both inside a parent container. I want to scroll the parent container and not the list, so I set scrollable: true to the parent container and scrollable: false to the list. but the list it's rendered with height: 0.

I did some more research here...
Nut sure, but the problem probably occurs, since only fit layout is allowed for list components.
I believe, if the scroller is set to false, the layout should be default... But this is not allowed by design.

A component is a component, and I should be able to put it in a container and let it overflow that container, no matter how much room it needs. What if the list was simply a multi-line paragraph that required me to set its height?

Breaking a so widely used component in a minor release is a bad idea.
I'll stick with v2.0.1.1 until 2.1 exits the beta stage, but it's a shame we can't get to know what Sencha developers think is the right approach with the new list component, and if this behavior will stick in the final version or not.