I can’t see selectors-4 on any of the popular accounts on github to raise issues there.
However there are a lot of unanswered questions on the specification and I just wondered where the best place to discuss them is (Obviously I’m aware of the mailing list however sometimes it doesn’t seem the best place until the idea actually has more weight than “I think it should have this syntax”, “Yeah, well I like this syntax”).
Issue 11 was the one I was currently interested in:
It seems that :blank may be a little ambiguous however is more specific than :-moz-whitespace-only which implies the element can’t be empty.
The best I could think of would be add :space which would match only elements with spaces in them, then to get :blank functionality you could use: el:matches(:space, :empty).
I considered something off the wall like :trim where most languages would see whitespace or not as acceptable, however I think it is more confusing than :blank.
I also considered :collapsable but again confusing.
I guess the prefix should match whatever gets settled for text-space-collapse vs white-space-collapse, unless this has been removed completely.
There is some bikeshedding for you all, I know how much you all like it hah.
I’m okay with :blank, not sure I see the value of using :whitespace-only or something else.
Also, I like the current semantics of :blank, equal to :matches(:empty, :whitespace-only). I’ve never had the use case of selecting an element that must contain a text node which must contain only whitespace. What I’ve had is trying to use :empty with an intent of “there is no non-whitespace text or child element”, and seeing it fail.
Yeah I read the mailing list a lot but rarely see any worth in adding threads there as that to me feels reserved for large sweeping changes or well structured research.
I have never felt comfortable to discuss pointless things like this on the mailing list.
I guess this all comes out of the modern tooling which @robin is leading.