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

The CSS Working Group just discussed `[css-selectors] Can you standardise a pseudo-element selector for file inputs?`, and agreed to the following:

* `RESOLVED: expose this selector and name it ::file-chooser`
* `RESOLVED: expose this selector and name it ::file-chooser button`

<details><summary>The full IRC log of that discussion</summary>
&lt;dael> Topic: [css-selectors] Can you standardise a pseudo-element selector for file inputs?<br>
&lt;dael> github: https://github.com/w3c/csswg-drafts/issues/5049<br>
&lt;dael> emilio: Apparently all others UI than FF have a pseudo-element for this.<br>
&lt;dael> emilio: Is anyone planning to remove it? If not, can we add a specific pseudo for this?<br>
&lt;dael> Rossen_: Is question about if component model for the control will change so there's no button?<br>
&lt;dael> emilio: No, question is that all of them have a button and all UI except FF expose as a pseudo element. ONly reason to not make a standard version is if underlying model will change. I don't see a reason not to add this unless there are objections<br>
&lt;dael> TabAtkins: Still vaguely uncomfortable about exposing internals of form controls, but I'm comfortable with this one. All files must have button and I expect will in future<br>
&lt;dael> emilio: Ideas on name?<br>
&lt;dael> TabAtkins: In issue works for me<br>
&lt;dael> Rossen_: Can we future proof more?<br>
&lt;dael> Rossen_: Currently ultra specific to the input type = file. If we're going down the path of exposing selectors to target form controls I would hope more generic so if there are other input types that can have a button that this selector will match with them<br>
&lt;dael> emilio: Not sure I agree. All different input types have values, mostly prefixed pseudo-elements. I don't think you want...I'd rather it be specific than potentially expand in the future and websites change b/c of that<br>
&lt;dael> TabAtkins: Comfortable with button name. This is a naming convention that we could extend<br>
&lt;jensimmons> I wanted to ask "how does this fit with the overall form control research project that's underway?" (Instead I hung up the call)<br>
&lt;dael> smfr: I don't like upload in the name. It's choose a file. Not sure it should look the same b/c this is apsecific behavior about trigger UI file selection. If it says only image types it opens photo picker. Name needs to be generic<br>
&lt;dael> emilio: Edge name is ::msbrowse<br>
&lt;smfr> ::file-chooser-button<br>
&lt;fremy> ::file-picker-button<br>
&lt;dael> Rossen_: WE spent quite a bit of time bikeshedding that name back when we expanded our control model. I think it was debated quite a bit and I was on the other side of the argument. If everyone else is fine with it, sure.<br>
&lt;dael> jensimmons: Curious about work around form control styling coming in the next few years. Will there be a pseudo-element for buttons? What's the names that have been discussed there.<br>
&lt;dael> TabAtkins: I believe gregwhitworth and Nicole Sullivan have been working on that and doing user research. Work is ongoing but not sure the results.<br>
&lt;dael> jensimmons: I know it's massive and lots of questions, but this feels like it should be designed in the context of that. Though I don't mean don't push for 2 years<br>
&lt;dael> TabAtkins: I feel you. I think the use cases and name are clear enough I think this would be an alright one off to do.<br>
&lt;dael> Rossen_: Sounds like general agreement around the reasoning to expose this. Naming-wise let's not spend hte hour bikeshedding. file-chooser or file-picker sort of fit what has been explained even if case you open an image gallery it's still a file<br>
&lt;dael> Rossen_: Can we pick one and move on? file-chooser or file-picker are good enough for now?<br>
&lt;fremy> +1 to either<br>
&lt;fremy> Rossen_: ^_^<br>
&lt;dael> Rossen_: I'll choose file-chooser. We can rename later<br>
&lt;jensimmons> I'm ok with file chooser or picker or upload, etc. I don't really like "browse" — it's far too generic in the context of "browser" and plus a younger generation of people don't really know what 'browsing files' means....<br>
&lt;dael> Rossen_: Obj to expose this selector and name it ::file-chooser<br>
&lt;dael> RESOLVED: expose this selector and name it ::file-chooser<br>
&lt;dael> RESOLVED: expose this selector and name it ::file-chooser button<br>
&lt;emilio> `::file-chooser-button`<br>
</details>


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

Received on Wednesday, 20 May 2020 16:21:41 UTC