Sass developers struggle to reuse selectors across media queries
In the cited Sass reports, developers wanted to share selectors across responsive contexts, but the compiler’s media-query boundary blocked `@extend`. They resorted to code gymnastics or hard-to-discover `@at-root` workarounds, making stylesheets harder to read and maintain. The reports date from 2013–14, so current demand and Sass behavior should be validated before building.
For sass/SCSS developers maintaining responsive stylesheets. Mentioned from Dec 2013 to Feb 2020 on GitHub.
5 different people described this problem in 2 separate discussions.
- Indie fit
- 2.0/10
- Pain
- 5.7/10
- Frequency
- 6.5/10
- Willingness to pay
- 0.0/10
- Momentum
- 5.0/10
- Who pays
- Professionals
- Competition
- Medium
- Build difficulty
- Medium
What people said
Quoted word for word. Follow a link to read the whole discussion.
I already had this need, and had to do some code gymnastics to get round this limitation. This gave things less flexible, and more difficult to read and maintain
In my experience this is one of the most often requested features in Sass, both verbally among my peers and from what I see in issue queues and comment threads on the internet
Build brief
See what to build and who will buy it
- 1 product idea with the smallest useful version and pricing
- 3 places to find your first customers
- 5 more quotes from people who have this problem
- Current workarounds, existing solutions and risks