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

Add new rule to disallow specific condition in @container queries #7635

Open
CosticaPuntaru opened this issue Apr 22, 2024 · 1 comment
Open
Labels
status: needs discussion triage needs further discussion

Comments

@CosticaPuntaru
Copy link

What is the problem you're trying to solve?

I want to be able to enforce mobile-first responsive design using @container, similar to media-feature-name-disallowed-list

What solution would you like to see?

support for rule

"container-feature-name-disallowed-list": [
	"max-width"
]

or a option for media-feature-name-disallowed-list to include @container

@Mouvedia Mouvedia added the status: needs discussion triage needs further discussion label Apr 22, 2024
@Mouvedia Mouvedia mentioned this issue Apr 22, 2024
5 tasks
@ybiquitous
Copy link
Member

@CosticaPuntaru Thanks for opening the discussion. The new rule's idea sounds interesting. But here, it seems that there are a few things that we need to confirm.

  • According to the CSS spec, there are no "container feature name", but <container-name> and <container-query>. So, we need to consider more proper name for the new rule.
  • According to the spec, <container-query> can include the <size-feature> syntax, which is the same as a media feature. The suggested rule seems to aim at this <size-feature> name.

To be honest, I'm not familiar with @container, so I'd like to see more use cases.

Ref https://developer.mozilla.org/en-US/docs/Web/CSS/@container

@ybiquitous ybiquitous changed the title container-feature-name-disallowed-list similar to media-feature-name-disallowed-list but for @container Add new rule to disallow specific condition in @container queries Apr 23, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
status: needs discussion triage needs further discussion
Development

No branches or pull requests

3 participants