You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
ATM we use the float–based element positioning, which isn't the most convenient way of building the interfaces. Flex would speed up the development, shorten the code and solve some issues that required JS solutions.
The only problem here is IE11 which has some issues with Flex but I'm not certain if they will be a problem to us. This must be checked.
The sooner we go with Flex, the better because ATM we're facing a major CSS refactoring (migration to PostCSS) in a couple of days anyway and the number of UI components isn't that big (yet).
The text was updated successfully, but these errors were encountered:
Having spent a lot of time on FlexBox with IE11 support, the bugs are not challenging to work around (largely, just have a good "reset" to normalize flexbox defaults, and then remember to always use flex: a b c;)
ATM we use the float–based element positioning, which isn't the most convenient way of building the interfaces. Flex would speed up the development, shorten the code and solve some issues that required JS solutions.
The only problem here is IE11 which has some issues with Flex but I'm not certain if they will be a problem to us. This must be checked.
The sooner we go with Flex, the better because ATM we're facing a major CSS refactoring (migration to PostCSS) in a couple of days anyway and the number of UI components isn't that big (yet).
The text was updated successfully, but these errors were encountered: