- From: Robert Flack via GitHub <sysbot+gh@w3.org>
- Date: Wed, 02 Nov 2022 19:58:16 +0000
- To: public-css-archive@w3.org
@fantasai sorry for the confusion, makes sense!
> * should the inset be incorporated into the startOffset / endOffset readouts? Or should those represent raw object bounds only?
I agree with your assessment, that startOffset and endOffset should probably incorporate inset calculations.
> * should the inset be a separate attribute? If so, as one sequence attribute inset or as startInset and endInset? (Personally, I think the latter is more understandable, even if the input object uses a sequence.)
I think you could make a similar argument that by exposing insets it makes it more ergonomic to pass one view timeline's insets to another, e.g.
```js
let timeline2 = new ViewTimeline({
subject: el,
insets: timeline1.insets
});
```
Though I think that's a fairly weak reason to do it and would be fine with it being separated into startInset and endInset since as you say this is more understandable.
--
GitHub Notification of comment by flackr
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/7748#issuecomment-1301160427 using your GitHub account
--
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 2 November 2022 19:58:18 UTC