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
It is like MicrosoftEdge/MSEdgeExplainers#377. Basically, if you're using the window segment API there is no way to know that the device is supporting spanning but it's not spanning currently.
That's because when the window isn't spanning getWindowSegments only return 1 (which is the same value as on a desktop/mobile). So, there is no way to invite the user to span the window to provide a better/optimized experience without using the CSS spanning MQ to do so.
@zouhir@kenchris what do you think? Should we address this or should we just say : use the MQs?
The text was updated successfully, but these errors were encountered:
GetWindowSegments returns 0 on desktop/mobile devices that can't have two segments. Just like spanning: none MQ wouldn't match on desktop/mobile platform that can't have two segments ever.
Add a method somewhere that developer can use to see if multiple segments are supported. A top level supportsMultipleWindowSegments on window just like getWindowSegments.
It is like MicrosoftEdge/MSEdgeExplainers#377. Basically, if you're using the window segment API there is no way to know that the device is supporting spanning but it's not spanning currently.
That's because when the window isn't spanning
getWindowSegments
only return 1 (which is the same value as on a desktop/mobile). So, there is no way to invite the user to span the window to provide a better/optimized experience without using the CSS spanning MQ to do so.@zouhir @kenchris what do you think? Should we address this or should we just say : use the MQs?
The text was updated successfully, but these errors were encountered: