On Fri, Aug 7, 2015 at 9:50 PM, Alex Harui <aha...@adobe.com> wrote: > One of my goals for FlexJS is to leverage as much code in the browser as > possible. That’s why there are button components that thinly wrap the > HTML button element. You can pay-as-you-go and select heavier buttons > that allow more complex skinning and/or styling. > > I thought we’d be able to leverage the browser’s layout code for vertical > and horizontal layout. The current version sets the children to > display:block or display:inline-block. That’s much less code than running > a loop on the children, figuring out margins, left/right constraints, etc, > and therefore less code to write, debug and maintain. >
I think it would be better if we start using the flexbox model [ http://caniuse.com/#feat=flexbox] Horizontal layout would be: display: flex; flex-direction: row justify-content: space-between; > > But these days, I’m starting to wonder if one of the benefits of FlexJS > will be in the availability of layouts that pretty much use > position:absolute to control everything. There are lots of funky rules > and workarounds for how browsers deal with display:inline-block, for > example. > Anyway, I’m wondering if there is anything, besides performance, we might > give up by giving up on display:inline-block and writing our own > horizontal layout. > I am worried we will end up with too many edge cases for responsive layout requirements. That said, we might end up doing layouts in code for more complicated layouts like coverflow, rolodex, time machine etc. that we support in Flex today. So I guess having Horizontal and Vertical layouts in code might be okay since they are simpler. Thanks, Om
