Re: [csswg-drafts] [css-selectors] Can you standardise a pseudo-element selector for file inputs? (#5049)

> I will note that there are a lot more search results for "file picker" than "file chooser". And also most of the ones for "file chooser" in quotes seem to be about some Java thing...

"file upload" is _way ahead_ in search volume when coupled with either [css](https://trends.google.com/trends/explore?q=file%20upload%20css,file%20chooser%20css,file%20picker%20css,file%20selector%20css), or [button](https://trends.google.com/trends/explore?q=file%20upload%20button,file%20chooser%20button,file%20picker%20button,file%20selector%20button). As I wrote in the [WICG draft thread](https://github.com/WICG/open-ui/pull/92):

> I agree with the `-button` suffix as the selector's purpose essentially dictates it. However, for consistency's sake, the verb really should be a choice between "upload" and "select"/"selector". The majority of standards documents for HTML and JavaScript refer to such controls as file upload, and the action performed as selection, and have done so for many years. What benefit is there to CSS authors in deviating from those conventions?
> 
> There is merit to each:
> 
> * the button triggers a file selection system but operating it doesn't guarantee a file upload attempt by the user; and
> * emphasising upload as the action is important because successful selection of any file immediately makes the file's name and contents available to running script, unlike the olden days when it was only a state of intent to upload upon form submission.

It's already "upload" in `::-webkit-file-upload-button` so why the change to "chooser"? I appreciate the speedy response to this issue, but I think making a new name instead of using the existing convention is a mistake.

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

Received on Tuesday, 26 May 2020 00:19:28 UTC