MicrosoftEdge / MicrosoftEdge/MSEdgeExplainers
[RFC] Change `spanning` media feature
@alisonmaher is already working on this.
Since Aug 20, 2020.
- Dominant language
- HTML
- Stars
- 1.4k
- Forks
- 286
- Avg merge
- 3d 1h
- Merged PRs (30d)
- 8
Description
We originally proposed spanning media feature with a set of a string-type values representing the hardware configuration (single-fold-vertical, single-fold-horizontal), and our idea for the future was to create new string values representing the screen topologies of that new hardware.

We believe the folks on this CSSWG thread https://github.com/w3c/csswg-drafts/issues/4736 have provided great suggestions that we are now strongly considering as alternatives to the currently proposed spanning media feature.
@fantasai has proposed:
display-span-x: <integer[1,inf]>
display-span-y: <integer[1,inf]>
@Crissov sort-of similarly proposed:
segmentation-x or horizontal-segments
segmentation-y or vertical-segments
Why do we like the above proposal?
What @fantasai has specified above makes the media-feature self-explanatory and follows a clear and deterministic convention, this increases the ergonomics of the API and helps developers to easily reason about the configuration they are willing to target, rather than keep having to look up the spec to understand what a dictionary of values actually maps to what hardware.
To discuss
-
any objections on moving forward with @fantasai's suggestion? more specifically, towards 2 separate media feature for horizontal and vertical display regions (logical or physical) and the values are of type
integer -
do you feel the phrase
display-span-xanddisplay-span-ynaturally covers devices with no separate physical displays such as Samsung's and Motorola's foldable devices?

-
other feedback items regarding this topic?
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.