Add following Media characteristics pseudo classes: - has-closed-captioning - has-audio - has-video - has-duration see: https://bugs.webkit.org/show_bug.cgi?id=59867
Created attachment 113042 [details] proposed patch
Comment on attachment 113042 [details] proposed patch Attachment 113042 [details] did not pass efl-ews (efl): Output: http://queues.webkit.org/results/10244612
(In reply to comment #2) > (From update of attachment 113042 [details]) > Attachment 113042 [details] did not pass efl-ews (efl): > Output: http://queues.webkit.org/results/10244612 forgot to put changes under #if ENABLE(VIDEO), will upload updated patch soon...
Created attachment 113046 [details] updated patch
Can someone from people on CC list review the patch please.
It is not clear to me what these are good for (even after reading the whatwg thread). CSS is not very good for styling things based on state of another element so these are fairly inflexible to use. A media controller needs scripting anyway. A full implementation of all pseudo classes would require quite a bit of code.
(In reply to comment #6) > It is not clear to me what these are good for (even after reading the whatwg thread). CSS is not very good for styling things based on state of another element so these are fairly inflexible to use. What do you mean by this? Styling based on state of an ancestor is a very common pattern in Web development. > A media controller needs scripting anyway. A full implementation of all pseudo classes would require quite a bit of code. Yep. That's certainly a cost. But the benefit is pretty nice too, albeit localized to media controls and those styling them. And yes, you would still need scripting to build a full-blown media controller, but with these pseudo-classes, you could totally get away with just CSS to skin existing controls.
(In reply to comment #7) > (In reply to comment #6) > > It is not clear to me what these are good for (even after reading the whatwg thread). CSS is not very good for styling things based on state of another element so these are fairly inflexible to use. > > What do you mean by this? Styling based on state of an ancestor is a very common pattern in Web development. Exactly. Ancestors only. Inflexible. Presumably you would occasionally want elements other than ancestors to be affected by the media state. > > A media controller needs scripting anyway. A full implementation of all pseudo classes would require quite a bit of code. > > Yep. That's certainly a cost. But the benefit is pretty nice too, albeit localized to media controls and those styling them. And yes, you would still need scripting to build a full-blown media controller, but with these pseudo-classes, you could totally get away with just CSS to skin existing controls. I think there is a whiff off adding features for the sake of adding features here. I think you should at least get some traction in whatwg first. I don't really feel very strongly about this either way. Just asking the potential reviewers to consider if this is really worth doing.
I mean "elements other than children"
> I don't really feel very strongly about this either way. Just asking the potential reviewers to consider if this is really worth doing. For what it's worth, I also have a similar doubt (even though I proposed this originally). There's a delicate cost/benefit balance, and I stand ambivalent in attempt to resolve it.
I am not an expert but it looked good addition to me and also because it was already discussed on WHATWG. I will cancel adding these classes as the advantages of having it are not clear.
Comment on attachment 113046 [details] updated patch Canceling r? as we don't have consensus that this is a good direction. Please feel free to reopen if you think this is incorrect.
WONTFIX for now based on lack of traction.