-
Notifications
You must be signed in to change notification settings - Fork 187
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
Support more breakpoints #202
Comments
+1 -- Also looking for the correct way to handle this in the latest versions of Primeflex -- the previously documented SCSS variables appear to have changed and we need to enable progressive support for larger breakpoints |
This works for me currently, but some proper documentation would be nice:
|
Hello, and thank you for the excellent work on PrimeFlex! I appreciate the utility and flexibility it provides. Currently, PrimeFlex defines breakpoints as follows:
However, I would like to request the addition of more breakpoints, similar to what Bootstrap offers. Bootstrap includes an extra small (xs) breakpoint and an extra-extra-large (xxl) breakpoint, which provide more granularity for responsive designs. Adding these breakpoints would make it easier to handle layouts for very small or very large screens, providing more flexibility for modern responsive design. For example, the updated $breakpoints map could look like this:
This change would align PrimeFlex more closely with other popular frameworks, making migration or integration smoother for developers. It would also provide more versatility for tailoring designs across a broader range of devices. Thank you for considering this enhancement, and I look forward to hearing your thoughts on this! Best regards. |
Is it possible to change the number of breakpoints? 4 is not too many, and different projects have different needs.
Bootstrap supports a dynamic number of breakpoints for example, that would be awesome!
The text was updated successfully, but these errors were encountered: