You might have misunderstood me. Thee are quite a few inconsistencies worked around already.
The advantage of the framework code is that we can include workarounds so end developers don’t need to. For example: Today I ran into flexbox inconsistencies in layouts. Safari behaves different than everyone else for nested flexboxes. I found one work-around for one scenario and I’m investigating another for a different one. Once I have the workarounds worked out, I will be able to fix the FlexJS layouts so it will work consistently across browsers. Basically, we can treat cross-browser inconsistencies as bugs to be fixed on the framework level. Harbs > On Aug 13, 2017, at 10:36 PM, Olaf Krueger <p...@olafkrueger.net> wrote: > >> There’s nothing really built in > > Mhh... but I wonder if FlexJS can not guarantee consistency through > different browsers and different platforms, could we really speak about a > cross platform framework then? > Or do I miss something? > > Thanks, > Olaf > > > > -- > View this message in context: > http://apache-flex-development.2333347.n4.nabble.com/FlexJS-Browser-compatibility-tp63828p63851.html > Sent from the Apache Flex Development mailing list archive at Nabble.com.
