-
Notifications
You must be signed in to change notification settings - Fork 58
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
Ability to set defaultBreakpoint
dynamically in nuxt module
#54
Comments
Hi @cainaf! I'm Maarten, the maintainer of Thank you for your request. I've been thinking about this feature for a while myself, but I could come up with any valid use-cases to implement it. The main question that keeps blocking me is: When do you have the ability to add this specific information the client-side request? Do you have any specific use-cases where this feature would benefit you? I'd love to explore this topic more. PS. |
Hello @vanhoofmaarten! Hope you're doing fine, thanks for your response!
I don't have full knowledge to confirm the best way, but I would guess this information can be inferred directly from Libs like express-useragent implements that parsing logic. Furthermore, some CDN providers will parse that information before forwarding request to origin. AWS cloudfront let you forward following headers to identify it's device type:
But again, I guess they just extract that information from
I have a nuxt application that relies on I've been using a double of |
Hello |
Hi, I haven't come around to implementing this feature (yet). I'm happy to accept Pull Requests. |
Feature Suggestion
Add the possibility to set the
defaultBreakpoint
dynamically when using nuxt module.Why?
To prevent misbehavior of components when reloading a page in a screen size that is not the default. Components that depends on
$mq
are wrongly shown or hidden whilevue-mq
is not fully loaded in the frontend application, causing a blink of very misplaced ui components for a few seconds.Suggested solution
With SSR it's possible to have a header telling the screen size of origin request. We could have something like:
The text was updated successfully, but these errors were encountered: