Re: [csswg-drafts] [web-animations-1] Dependency on CSSPseudoElement (#4301)

The CSS Working Group just discussed `Dependency on CSSPseudoElement`, and agreed to the following:

* `RESOLVED: Pseudo elements are targeted via a parent plus a pseudo selector`

<details><summary>The full IRC log of that discussion</summary>
&lt;dael> Topic: Dependency on CSSPseudoElement<br>
&lt;dael> github: https://github.com/w3c/csswg-drafts/issues/4301<br>
&lt;rego> rego: present+<br>
&lt;dael> Steven: I'm hoping this is a rubber stamp. Hopefully everyone has read<br>
&lt;AmeliaBR> s/Steven/smcgruer /<br>
&lt;astearns> s/Steven/smcgruer/<br>
&lt;dael> Steven: We have a problem where CSSPSeudoElement has a lot of questions. For animations events and objects want to spec Pseudo element by target being parent element. Similar to animations nad transitions<br>
&lt;dael> smgruer: We expect this is how all will have to for for pseudo elements. No way to change events that happen today.<br>
&lt;dael> smcgruer: Want to make sure makes sense for group<br>
&lt;dael> florian: There was another conversation on speudo events for highlighting and discussed with editing TF. Opinion of the Editing TF is it was inadequat so let's be careful how we use/expose<br>
&lt;dael> florian: Not expert, but there was discussion on changing how looks/works<br>
&lt;dael> Rossen_: I think the discussion florian referring to for highlight API were close to what's being proposed. From last I heard they want to start taking more dependency on this prop model. Another was inking input want similar exposure for various types of actions and states. Want to be able to target similar eventing model<br>
&lt;dael> Rossen_: I have read the proposal, I don't think it's controversial. Want to hear from more people working in this space.<br>
&lt;dael> Rossen_: Not hearing any.<br>
&lt;dael> Rossen_: Are you looking for a resolution smcgruer? That accepts the proposal?<br>
&lt;dael> smcgruer: Yeah<br>
&lt;dael> fantasai: I wanted to ask if birtles has weighed in and what's his position<br>
&lt;dael> smcgruer: My understanding is he agrees. Her was part of the discussion. But I can't represent him directly<br>
&lt;dael> Rossen_: I don't believe he was opposed. We can re-open and continue if it's not complete. It doesn't come across that birtles is against in the thread.<br>
&lt;dael> Rossen_: I propose we resolve and if there's additional conversations we ca re-open<br>
&lt;dael> fantasai: Okay with that is assumption is correct<br>
&lt;dael> AmeliaBR: What's the exact proposal?<br>
&lt;fantasai> s/is/if/<br>
&lt;dael> smcgruer: Prop: Animations have a target element. We prop for animations targetting pseudo elements is the target is the parent and an additonal selector that lets you know which the new element it<br>
&lt;dael> Rossen_: Pseudo elements are targeted via a parent plus a pseudo selector<br>
&lt;dael> AmeliaBR: Has anyone thought about forward compat for a pseudo element dom object?<br>
&lt;dael> smcgruer: Not extensively. That's fair. Problem in general is event targeting in general will have to solve that<br>
&lt;dael> AmeliaBR: True. We have events where event target is the element.<br>
&lt;dael> Rossen_: Even if go down path of exposing pseudo element as objects need to have a way to target through selectors. That way will have to work here. Only change to model is how to get to event target.<br>
&lt;dael> Rossen_: If we expand the pseudo family we have to figure out how to select. Not unique to this proposal<br>
&lt;dael> Rossen_: Objections?<br>
&lt;dael> RESOLVED: Pseudo elements are targeted via a parent plus a pseudo selector<br>
</details>


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

Received on Wednesday, 16 October 2019 16:12:02 UTC