Totally. I was not trying to say that we should not have layouts which rely on browser layout. I was just suggesting that we probably *also* want layouts which do hard positioning.
Carlos’ position of trying to stick to pretty HTML and CSS as much as possible is probably one which many web designers will relate to. The thing we should try to avoid is mixing absolute positioning and css positioning of elements. Mixing the two probably gives the worst performance. I am trying to stick to the topic which is how to enable measuring and deferred layout when needed, but avoid it when not. Harbs > On Mar 27, 2018, at 7:38 AM, Alex Harui <[email protected]> wrote: > > Fundamentally, Royale should not force anyone into one way of thinking or > the other regarding layout and css or really anything. This is why I'm > not in favor of putting any deferred computation in the core. I think the > key discovery so far is that LayoutBase was forcing every layout to > compute the width/height. That does not fit into the above philosophy. > Let's remove that, and fix the layouts that were counting on it. > > It will be totally fine of some layouts go back and set width/height or > even position:absolute and left and top. Other layouts should just set > display and let the browser do the work. The key thing is that the code > should not make assumptions. Can we just agree to do that?
