- From: Mason Freed via GitHub <sysbot+gh@w3.org>
- Date: Wed, 12 Mar 2025 21:28:14 +0000
- To: public-css-archive@w3.org
> > Also, what if a developer wants tO replace the ::file- selector -button with their > > own custom element button? > > How common is this? > > Most customisations I've done in the past were essentially hiding the label entirely and then making the button an icon (like a paper clip) which I think the pseudo would allow provided I could set the content to an empty string (with an alt fallback value) and using background-image. Was going to respond here, but decided to open a specific issue instead: https://github.com/w3c/csswg-drafts/issues/11929 TL;DR: It seems somewhat common for design systems to have a standard "button" component. And it also seems natural to want to use that component for all "buttons" that users see. > > allowing a site to misrepresent the file that was selected? > > This is already doable today via various mechanisms? Yeah, that's a fair point I guess. So perhaps we also need a pseudo for the file display text field? -- GitHub Notification of comment by mfreed7 Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/11847#issuecomment-2719172537 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 12 March 2025 21:28:15 UTC