- From: Joey Arhar via GitHub <sysbot+gh@w3.org>
- Date: Mon, 18 Nov 2024 18:52:57 +0000
- To: public-css-archive@w3.org
> > I really don't like the button having an all: unset with the latest UA style update. It creates a confusing developer experience as most will expect a button to have certain things, such as a display property set to inline-block, letting you add paddings right away. > > Not sure where you see `all: unset`? 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. -- GitHub Notification of comment by josepharhar Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/10857#issuecomment-2483858032 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Monday, 18 November 2024 18:52:58 UTC