Skip to content

New CSS principle: Describe when 'auto' is an appropriate property value #568

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

Open
jyasskin opened this issue Apr 10, 2025 · 0 comments
Open

Comments

@jyasskin
Copy link
Contributor

This was brought up in our discussion of w3ctag/design-reviews#1001 (comment) and w3ctag/design-reviews#1011 (comment).

It seems to be tempting for CSS feature designers to use 'auto' in more situations than it's really appropriate, and there ought to be guidance on when it is appropriate. We'll need help from CSS experts to figure out that guidance. (cc @fantasai @tabatkins) Some components seem to be:

  • let the browser do what it thinks is best.
  • the behavior that does a pretty good job for most pages.
  • the behavior that should be the default, even if we can't make that happen for compatibility reasons.
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

1 participant