Skip to content
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

Figuring out if the device can span but is not currently spanning. #6

Open
darktears opened this issue Sep 8, 2020 · 2 comments
Open

Comments

@darktears
Copy link

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?

@kenchris
Copy link

kenchris commented Sep 9, 2020

So you want a DOM API? Maybe on the window.screen or the new Window Enumeration API?

@darktears
Copy link
Author

Well we multiple options:

  • 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.

Just random ideas.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants