Sébastien Lepage

An exception should be thrown, or a log at least

We could probably stick to UIData, and get rid of UITabPanel. Needs some thinking

Arf doesn't look good... specially if same problem happen with both impl... I tried without a composite and works fine. If you debug `Timeline#getValue`, you'll see that it's trying to...

I started few weeks ago on refactoring timeline, nothing big. I'll submit a PR for review and hopefully ready for 11

> Arf doesn't look good... specially if same problem happen with both impl... I tried without a composite and works fine. Yes, don't use composite 😄 But on a more...

Yeah... First, like Thomas mentionned the component needs some love (I have to check if I can find the refacto I started few years back...) and second, you better off...

Not sure I follow, every `UIComponent` has a state...If by state, you mean your bean then I'm not aware of the relation between this and the type of reusable component...

Again, I have no idea what you mean by state, so I think a bit of reading is required: https://stackoverflow.com/a/6822269/4605161

The link you found is really useful to understand the issue, plus it's BalusC certified therefore I'm posting just to highlight it 😄 : https://stackoverflow.com/a/11961132/4605161

I think `ColumnGroup#type` with `frozenFooter` and `frozenHeader` were meant exactly for this use case (to have col groups + frozen columns) I think it's been fixed in my MR for...