- From: CSS Meeting Bot via GitHub <sysbot+gh@w3.org>
- Date: Wed, 26 Sep 2018 16:30:42 +0000
- To: public-css-archive@w3.org
The CSS Working Group just discussed `decide on :blank`, and agreed to the following: * `RESOLVED: Add :blank for input selectors` <details><summary>The full IRC log of that discussion</summary> <dael> Topic: decide on :blank<br> <dael> github: https://github.com/w3c/csswg-drafts/issues/1967<br> <dael> fantasai: There's a realted issue to decide first.<br> <fantasai> https://github.com/w3c/csswg-drafts/issues/1283<br> <jensimmons> I definitely prefer west coast of North America. Let’s pick a major hub city for international flights — like Vancouver or LA. We also have a lot of office space available in San Fran, Mountain View…. lots of options.<br> <dael> fantasai: Adding a selector for blank input fields<br> <dael> fantasai: If we want to do that black is the best name. If we do that we can't use blank for meaning empty.<br> <dael> fantasai: Comments, thoughts?<br> <dael> fantasai: We can reserve the name and not resolve to add or decide we don't want to do this.<br> <dbaron> s/Singapore is easier to get to right now/I'd prefer Japan twice over Singapore or Malaysia. Between Singapore and Malaysia, Singapore is easier to get to right now due to competition in SFO-SIN flights./<br> <TabAtkins> Okay, LA is out too. It's got setups for *much larger* meetings, and *slightly smaller* meetings (16-18), but nothing in our sweet spot.<br> <dael> dauwhe: Also have blank selector in pages<br> <bkardell_> :blank seems right for inputs to me<br> <Rossen_> s/ do that black is the best name/ do that blank is the best name/<br> <dael> fantasai: Yeah. That's a different scope so not a naming conflict<br> <dael> Rossen_: Opinions?<br> <fantasai> a) Decide to add :blank for input selectors<br> <dael> fantasai: Options [in IRC]<br> <fantasai> b) Decide to reserve :blank but not resolve to add yet<br> <fantasai> c) Decide we either don't care about blank inputs or don't want :blank for them regardless<br> <dael> fantasai: We should decide on a/b/c and then go back<br> <dael> Rossen_: This was 1283, right?<br> <dael> fantasai: Yeah<br> <dael> github: https://github.com/w3c/csswg-drafts/issues/1283<br> <dael> Rossen_: I see one opinion<br> <dael> fremy: I just looked and I like using a function on empty and specify if whitepsace is a parameter.<br> <dael> fantasai: That's issue 1967<br> <dael> dbaron: One proposal in the past is have an attribute selector like syntax that you can use with form control. A way to put form value into attribute selector syntax.<br> <dael> fantasai: Would it handle all the relevent use cases?<br> <bkardell_> i would think it would matter for input<br> <dael> dbaron: white space variations on empty string? OR does that not matter as much?<br> <dael> fantasai: Don't know. If we go with functional notation for empty we might want same here.<br> <dbaron> e.g., input[:value=""]<br> <dael> Rossen_: We can add 'ish' param ^-^<br> <chris> lol<br> <fremy> @Rossen_: +1 :)<br> <dael> Rossen_: Back to original options, can we narrow those down?<br> <dael> fantasai: I suggest a or b which means not use blank in 1967<br> <bkardell_> are we not considering @dbaron's idea<br> <dael> Rossen_: 1283 is we're supposed to use blank. That's option a<br> <dael> fantasai: I think for the question of blank inputs we can go with dbaron option or we can decide to reserve blank or we do both.<br> <bkardell_> can we say the value is trim'ed in dbaron's?<br> <dael> fantasai: Is blank a thing we would want to apply to inputs or empty elements that might contain white space<br> <dael> Rossen_: Opinions?<br> <dael> nigel: I like the input value idea, it's nicely extensible. If you need a keyword is an interesting question. You can also define a regex and have a valid/invalid keyword.<br> <fantasai> nigel, see Chapter 12 in https://www.w3.org/TR/selectors-4/<br> <dael> nigel: For input controls, nonvalid and invalid are the obvious catagories as a min. If you need a test for particular strings is a bit much<br> <dael> fantasai: Have required and optional, but we don't have hey is this input empty or not.<br> <bkardell_> nigel I think part of the question is still whether " " is the same as "" or null<br> <dael> tantek: I don't hear strong opposition to blank [missed]<br> <dael> fantasai: Emty wouldn't work on inputs because they'r empty<br> <dael> tantek: I think I lean toward a<br> <dbaron> s/tantek/gregwhitworth/ (twice)<br> <dael> nigel: Blank being different from some whitespace can be considered to tbe the same as opposed to empty which can be literally the null string<br> <dael> gregwhitworth: I don't disagree but I feel we're in a weird world with empty and invalid. Invalid would hit the regex pattern I think.<br> <dael> gregwhitworth: Trying to solve a lot of same problems with 3 classes. THat's prob why fremy wanted to lean toward functional. I think we can bikeshed name later but I don't know anything better.<br> <bkardell_> dbaron's thing sidesteps the naming issue if we can say the value is trimmed?<br> <fremy> @gregwhitworth: I was thinking about `:empty(value)` for instance<br> <dael> Rossen_: I agree with gregwhitworth. I would prefer to make mroe progress so we can go back to 1967.<br> <dael> Rossen_: Objections to "Decide to add :blank for input selectors"<br> <dael> RESOLVED: Add :blank for input selectors<br> <dael> Rossen_: nigel to gregwhitworth 's point we might come back and bikeshed<br> </details> -- GitHub Notification of comment by css-meeting-bot Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/1283#issuecomment-424783273 using your GitHub account
Received on Wednesday, 26 September 2018 16:30:51 UTC