The reasons for only having a onDesktop combinator until now were that we wanted to try a mobile-first approach on our product development (which has clearly not caught on or worked very well), and we thought only specifying mobile and more general styles and overriding them with desktop-specific settings was enough.
The second assumption can make it cumbersome to encode specific styling rules, like when the desktop style should use a component's defaults while the mobile one should override them.
The reasons for only having a
onDesktopcombinator until now were that we wanted to try a mobile-first approach on our product development (which has clearly not caught on or worked very well), and we thought only specifying mobile and more general styles and overriding them with desktop-specific settings was enough.The second assumption can make it cumbersome to encode specific styling rules, like when the desktop style should use a component's defaults while the mobile one should override them.