> AFAICT, what's happening here is that the layout works "properly" in the > sense that the tables inside the various LayoutPanels are in fact laid out > as requested. The problem is that children nested *inside* table cells don't > take up the entire cell in standards mode, even if their width/height are > set to 100%. This is one of the biggest mistakes (IMNSHO) in the CSS > standard, but there's little to be done about that now. > > I believe Tab/DeckPanel are going to have to be among the widgets for which > we build layout-aware implementations. This would eliminate this problem by > eliminating the <table>. I'm going to be reviewing and checking in > implementations of the widgets described in the layout design doc over the > next week or so. Any help you could provide by reviewing their APIs and > behaviors would be greatly appreciated. >
Thanks a lot Joel for your precious answer. This topic is really challenging and the idea that consist to build an entire layout framework on top of 4 CSS properties is just crazy. Looking forward for the next patches/evolutions and you can obviously count on me for any kind of review I could provide (let me know if you prefer private mails or a contrib broadcasted mail) Sami ps: I will probably tease bobv now that I have spent time on the last deRPC changes ;-) --~--~---------~--~----~------------~-------~--~----~ http://groups.google.com/group/Google-Web-Toolkit-Contributors -~----------~----~----~----~------~----~------~--~---
