-
Notifications
You must be signed in to change notification settings - Fork 2.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Stack/Flex Convergence #16791
Comments
February Project cycleGoals:
Stretch goals:
|
Update:
|
Here's some links that I just quickly grabbed that are in Flex/Stack layout domain:
My hypothesis is that folks would like the feature set of CSS Flexbox in a React based package - specifically for just 1D horizontal/vertical children layout. Hope this helps! |
@JustSlone I've added some feedback on the Open UI PR and can understand the difficulty you noted. This may be one that you find is specific and helpful to React. From a convergence standpoint, I don't see us adding an abstraction like this in the form of a component for the web components. Previously, in our FAST React packages we had a composable react-based layout package built off CSS Grid to explicitly offer what @paulgildea called out above. When we shifted to focus on web components, we had some asks if there would be a web component version, but in the case of custom elements it seems like an unnecessary abstraction of the platform which only adds complexity. All that said, here's a link to our (now deprecated/archived) package which may be beneficial for your research :): https://github.com/microsoft/fast-react/tree/master/packages/react/fast-layouts-react#fast-layouts-react I'm happy to walk you through what we did and our reasoning for it if you like. |
Thanks for the feedback and CR, @chrisdholt, I've gone ahead and answered your points on the research PR. |
Update:
|
Update:
Goal for Feb:
|
Update - 3/1
Goals for March:
|
Goals for March:
Stretch goal:
|
Update:
In progress:
|
Update:
|
Linking #17923 as the implementation relies on CSS vars and without guaranteeing their uniqueness Flex cannot be used inside of another Flex and user variables might colide with Flex. |
Over the past days there were discussions about Flex and the concerns of performance/bundle size vs the benefits we get from a component like it.
Next steps will be to come up with a migration guide and removing the existing implementation. |
Preparation:
Conclusion
The text was updated successfully, but these errors were encountered: