Open
Bug 1350461
Opened 7 years ago
Updated 2 years ago
DevTools support for scroll timelines
Categories
(DevTools :: Inspector: Animations, enhancement, P3)
DevTools
Inspector: Animations
Tracking
(Not tracked)
NEW
People
(Reporter: botond, Unassigned)
References
(Depends on 1 open bug, Blocks 1 open bug)
Details
In bug 1321428, I will be landing an initial implementation of scroll timelines, which are part of the WIP scroll-linked animations spec [1]. I haven't yet thought much about what, if any, support the feature will need from DevTools. For now, I'm just filing this tracking bug in advance of sending out an "Intent to implement" email. [1] https://wicg.github.io/scroll-animations/
Comment 1•7 years ago
|
||
Brian and/or Daisuke might have ideas about what kind of support we will need already.
Component: Developer Tools → Developer Tools: Animation Inspector
Flags: needinfo?(dakatsuka)
Flags: needinfo?(bbirtles)
Comment 2•7 years ago
|
||
I suppose we need to represent the different timelines, perhaps as separate "subheadings" in the animations panel? i.e. group them by timeline with the default document timeline first, followed by other timelines (ordered by number of active animations? earliest start time?). In fact, we should probably already be doing this for timelines created using `new DocumentTimeline()`. We'll need labels to these timelines too (e.g. 'Scroll timeline for <div#container>' or something like that). It probably makes sense to design the animation grouping feature at the same time so that the interaction between the two features makes sense. The other difference is that we shouldn't just assume these scroll timelines advance at a fixed rate. Instead we probably need to query the timeline's currentTime every frame.
Flags: needinfo?(bbirtles)
Comment 3•7 years ago
|
||
Inspector bug triage (filter on CLIMBING SHOES).
Severity: normal → enhancement
Priority: -- → P3
Updated•6 years ago
|
Product: Firefox → DevTools
Updated•5 years ago
|
Flags: needinfo?(dakatsuka)
Updated•3 years ago
|
Updated•2 years ago
|
Severity: normal → S3
You need to log in
before you can comment on or make changes to this bug.
Description
•