- From: CSS Meeting Bot via GitHub <sysbot+gh@w3.org>
- Date: Wed, 28 Apr 2021 16:50:12 +0000
- To: public-css-archive@w3.org
The CSS Working Group just discussed `[selectors-4] Add a :media pseudo-class, to match the set of elements matching the media pseudo-classes`, and agreed to the following: * `RESOLVED: Close no change` <details><summary>The full IRC log of that discussion</summary> <dael> Topic: [selectors-4] Add a :media pseudo-class, to match the set of elements matching the media pseudo-classes<br> <dael> github: https://github.com/w3c/csswg-drafts/issues/6237<br> <dael> TabAtkins: As of a week or two ago had 2 pseudo classes that applied ot media. playing and paused. mutually exclusive. All elements not playing are pause.<br> <dael> TabAtkins: We agreed on edits from hober adding additional media pseudoclasses to match additional states. I realized this property that you could always select on one pseudoclass no longer applied. Example: muted. Select all not muted you can't use Not muted b/c selects everything on page<br> <dael> TabAtkins: Suggestion to help authors with this which is pseudoclass to just select media elements<br> <dael> TabAtkins: A few obj in issue. leaverou_ pointed out requests in the past to select MQ as selector so it mixes into selectors and name for that would be media<br> <dael> TabAtkins: emilio pointed out we have audio and video and now that we have :is it's not hard to get the same effect as you had before is pseudoclass<br> <Rossen_> q?<br> <dael> TabAtkins: Both are reasonable. Don't know if enough to sink it. I still think might be valuable to do something in this relm. What do others think? Not sure which way to go<br> <hober> q+<br> <dael> florian: Question. When you use pause it only gives you paused media elements?<br> <dael> TabAtkins: Yeah. Every single media elements is either playing or paused. But b/c no non-muted psuedo class we no longer have that property<br> <dael> florian: And can't solve by adding opossite of those introduced<br> <dael> TabAtkins: Could. Feels weird to add explicitly negated version when we have pseudo class negation<br> <dael> florian: But not same meaning<br> <leaverou_> q+<br> <dael> TabAtkins: Yeah.<br> <emilio> q+<br> <Rossen_> ack hober<br> <dael> hober: I think TabAtkins is right it's a real problem. Sympathetic to emilio point that :is audio|video is enough. Worry it's not fufutre proof. If we add another media feature sites will not match the new ones<br> <dael> hober: Slightly prefer adding a new pseudoclass but could live with leaving it to :is<br> <dael> hober: Don't care for adding negated pseudoclasses for all the new ones. Explosed number in a way that feels distasteful, but it's an aesthetic preference<br> <dael> TabAtkins: I think at this point I'm okay going with emilio and if we introduce more media elements we can revisit this so we don't have to negotiate futureproofing with media pseudoclass<br> <dael> leaverou_: I wanted to ask if we have sufficient evidence that authors want to target all media elements in a way. Stylesheets trying to target non-muted media elements? Feel it would be all video or audio<br> <fantasai> +1 leaverou_<br> <dael> hober: One use case is in user stylesheet. Looking at a website, something obnoxious happening and I can't find it to make it stop<br> <bkardell_> exxtension too<br> <dael> Rossen_: Good use case.<br> <bkardell_> s/extension/it would be useful in extensions<br> <Rossen_> ack leaverou_<br> <Rossen_> ack emilio<br> <dael> emilio: Wanted to mention there is precident for explicit negation with readwrite and readonly. You could argue that for website authors having media pseudoclass...argument hober made makes sense but can flip. New media elements would have selectors that didn't match start matching. Can go both ways.<br> <dael> emilio: I don't care either way, but there is precedent for negation<br> <dael> TabAtkins: That precedent exists in same way as playing and paused. Explicit differnet states. If name is not-x is what feels weird<br> <dael> TabAtkins: Think we're reasonably agreeing to close no change and rely on :is<br> <fantasai> +1 to close no change for now<br> <dael> emilio: Sounds good<br> <leaverou_> +1 to close<br> <dael> Rossen_: When seeking will one apply? both? none?<br> <dael> TabAtkins: I think playing<br> <dael> hober: Buffering and stalled playing still matches. I don't remember if new spec text says for seeking. Might be good followup<br> <Rossen_> q?<br> <dael> TabAtkins: Yeah, could use clarification<br> <tantek> possibly related: we have pseudo-classes for partially loaded images right? (that are still loading)<br> <TabAtkins> OH wait lol, we just have a :seeking pseudoclass now<br> <dael> fantasai: On queue to agree with leaverou_ and emilio. Close no change. If we need clarification add resolution<br> <TabAtkins> So, uh, obviously that's the one that matches when you're seeking<br> <dael> hober: Clarification shouldn't be always one or the other for seeking. Can used seeker to search playing or paused. Need to say unlike buffering or stalled you might be playing or paused when seeking<br> <dael> Rossen_: Seek has no change to the last known state of playing or paused. Fair?<br> <dael> hober: I think so<br> <dael> Rossen_: Prop: Close no change<br> <dael> hober: Can we also add action to write clarification?<br> <dael> action hober add text for Seek has no change to the last known state of playing or paused<br> <dael> RESOLVED: Close no change<br> </details> -- GitHub Notification of comment by css-meeting-bot Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/6237#issuecomment-828611819 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 28 April 2021 16:50:14 UTC