Ckeditor5: Research CSS flex box layout in the UI
ATM we use the float鈥揵ased 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).
oleq
All 3 comments
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;)
mwadams
on 3 Nov 2017
What's the status of this? Didn't we move to flex?
Reinmar
on 5 Apr 2018
We use flex across the UI ATM. I consider the topic closed.
oleq
on 6 Apr 2018
Related issues
hybridpicker
路
3Comments
wwalc
路
3Comments
benjismith
路
3Comments
Reinmar
路
3Comments
devaptas
路
3Comments
Most helpful comment
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;)