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
When using a calcite-maps app on my ipad, which device-width is 768px, the app behaves like on a mobile device (e.g. the panels are full screen). When i took a look on the calcite-maps.css-file, it seems, that switching to mobile behaviour happens, when the device-width is equal oder smaller than 768px
In the calcite-maps.js on the other hand, there is a variable "isMobile", which is set to "true", if device-width is smaller than 768px.
It seems to me, that it is not exactly clear, what happens, when the device-with is exactly 768px. The treatment in css and javascript seems to be incosistent. In my opinion, in this case the app should use the non mobile behaviour, because i think it is for example not necessary that the panels open full screen on a tablet.
The text was updated successfully, but these errors were encountered:
When using a calcite-maps app on my ipad, which device-width is 768px, the app behaves like on a mobile device (e.g. the panels are full screen). When i took a look on the calcite-maps.css-file, it seems, that switching to mobile behaviour happens, when the device-width is equal oder smaller than 768px
efor example:
@media ( min-width :769px) {
.visible-mobile-only {
display: none !important
}
}
In the calcite-maps.js on the other hand, there is a variable "isMobile", which is set to "true", if device-width is smaller than 768px.
It seems to me, that it is not exactly clear, what happens, when the device-with is exactly 768px. The treatment in css and javascript seems to be incosistent. In my opinion, in this case the app should use the non mobile behaviour, because i think it is for example not necessary that the panels open full screen on a tablet.
The text was updated successfully, but these errors were encountered: