Re: [csswg-drafts] [css-ui] UA stylesheet for appearance:base `<select>` (#10857)

> I just added it to the issue description. It came out of my code review to add display:contents in chromium. I added a comment explaining why it is needed.

I understand the reason behind it, but I feel like it's "one more caveat" that people will trip over a few times.

for example, a developer might quickly start prototyping something :
```
select > button { 
  padding: 1cqmin; 
  border: 1px solid #c0ffee; 
}
```

After doing that, a developer goes to watch the change to the CSS and wonders why the button doesn't have padding. Looks it up and finds out that he/she needed to add the `display` property, in contrast to a button anywhere else, where user-agent styles are set to `display: inline-block`.

That being said, I'm not trying to push on changing this, but I believe it is something we should be aware of when going forward with this. It can potentially be a common pitfall / frustration for developers, especially at first.  It's at the least going to bring a small amount of confusion.




-- 
GitHub Notification of comment by brechtDR
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/10857#issuecomment-2485363349 using your GitHub account


-- 
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config

Received on Tuesday, 19 November 2024 10:55:50 UTC