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
This might seem like a tiny detail, but my workplace, which has used Quasar since before I started working there, has based internal media queries on this standard. And that has resulted in some interesting problems where a webpage will behave strangely on a screen of size 600px, because it turns out a bug causes media queries with max-width: 599.99px to register as 600px, which is presumably why your implementation uses 599.98px instead.
Description
https://quasar.dev/style/visibility#window-width-related says that the xs screenwidth goes up to 599.99px, but inspecting an element using quasar rules reveals that it uses a breakpoint of 599.98px.
This might seem like a tiny detail, but my workplace, which has used Quasar since before I started working there, has based internal media queries on this standard. And that has resulted in some interesting problems where a webpage will behave strangely on a screen of size 600px, because it turns out a bug causes media queries with max-width: 599.99px to register as 600px, which is presumably why your implementation uses 599.98px instead.
Documentation Section URL
https://quasar.dev/style/visibility#window-width-related
Flavour
None
Areas
Components (quasar)
The text was updated successfully, but these errors were encountered: