Unfortunately that's over-simplification of the problem. 10-15 years we were told that use of <table>s for layout purposes was terribly wrong. Without any reli

Unfortunately that's over-simplification of the problem. 10-15 years we were told that use of <table>s for layout purposes was terribly wrong. Without any reliable alternative mechanism. Here is my proposal to W3C CSS WG to add flow property and flex units: https://www.terrainformatica.com/w3/flex-layout/flex-layout.htm https://www.terrainformatica.com/w3/flex-layout/flex-layout.... It covers as flexbox as grid features under the same mechanism. Yet it establishes robust framework for other layout methods. Note it is dated April, 5, 2009. It took us almost 10 years to have something matching that. So neither W3C process nor WHATWG process is perfect - there is no reliable feedback from customers (web designers) to browser vendors. What if browser would provide us just abstract DOM with minimal HTML/CSS implementation and some extensibility/plug-ins mechanism with something like Java. In this case we, the community, can provide better implementations: main { flow: HolyGrailLayout(params) url(/layouts/HolyGrail.class); } <main> <header> <footer> <aside> </main> So instead of waiting for the weather for 10 years we will do something literally tomorrow when we need it. In this case W3C will be able to perfectly fit its role - high-level management of all this. No one can manage the reality up to need of toilet paper in full. USSR tried and where did it go?