(In reply to Nicolas Chevobbe [:nchevobbe] from comment #2) > I'm seeing that there's now an `animation-timeline` property, which seems to be used in combination with the `scroll-timeline` property, so I guess that in the rule view, we could show which elements sets the `scroll-timeline` property for the `animation-timeline` set on a rule? Similar to what we did for container queries (see https://twitter.com/FirefoxDevTools/status/1595080892417945600) so devs could navigate more easily between the "scroller" and the "target" > > Boris, I was trying to test this a bit but it looks like the spec changed a bit since you filed the bug so I'm not sure how I can get a working demo, could you point me to something or give me a simple example? > > When you said it needs DevTools support, do you have something specific in mind other than "it shouldn't break the inspector" ? > > Finally do you have an estimate when this will be enabled in Nightly/by default? It would help us prioritize this if this is close to completion :) > Thanks! The spec keeps changing recently, and so I think it may not be enabled by default before the end of this year. I keep my ni until I think it's ready to go to next step. At that moment, I will provide the example and what we should have in the inspector. So for now I think it's fine to leave this bug with a lower priority.
Bug 1731112 Comment 3 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
(In reply to Nicolas Chevobbe [:nchevobbe] from comment #2) > I'm seeing that there's now an `animation-timeline` property, which seems to be used in combination with the `scroll-timeline` property, so I guess that in the rule view, we could show which elements sets the `scroll-timeline` property for the `animation-timeline` set on a rule? Similar to what we did for container queries (see https://twitter.com/FirefoxDevTools/status/1595080892417945600) so devs could navigate more easily between the "scroller" and the "target" > > Boris, I was trying to test this a bit but it looks like the spec changed a bit since you filed the bug so I'm not sure how I can get a working demo, could you point me to something or give me a simple example? > > When you said it needs DevTools support, do you have something specific in mind other than "it shouldn't break the inspector" ? > > Finally do you have an estimate when this will be enabled in Nightly/by default? It would help us prioritize this if this is close to completion :) > Thanks! The spec keeps changing recently, and so I think it may not be enabled by default (i.e. release/beta) before the end of this year. I keep my ni until I think it's ready to go to next step. At that moment, I will provide the example and what we should have in the inspector. So for now I think it's fine to leave this bug with a lower priority.
(In reply to Nicolas Chevobbe [:nchevobbe] from comment #2) > I'm seeing that there's now an `animation-timeline` property, which seems to be used in combination with the `scroll-timeline` property, so I guess that in the rule view, we could show which elements sets the `scroll-timeline` property for the `animation-timeline` set on a rule? Similar to what we did for container queries (see https://twitter.com/FirefoxDevTools/status/1595080892417945600) so devs could navigate more easily between the "scroller" and the "target" > > Boris, I was trying to test this a bit but it looks like the spec changed a bit since you filed the bug so I'm not sure how I can get a working demo, could you point me to something or give me a simple example? > > When you said it needs DevTools support, do you have something specific in mind other than "it shouldn't break the inspector" ? > > Finally do you have an estimate when this will be enabled in Nightly/by default? It would help us prioritize this if this is close to completion :) > Thanks! The spec keeps changing recently, and so I think it may not be enabled by default (i.e. release/beta) before the end of this year. I keep my ni until I think it's ready to go to next step, or we have a clear time frame to enable this in Nightly. At that moment, I will provide the example and what we should have in the inspector. So for now I think it's fine to leave this bug with a lower priority.