- From: Fredrik Söderqvist via GitHub <sysbot+gh@w3.org>
- Date: Fri, 16 Apr 2021 08:51:56 +0000
- To: public-svg-issues@w3.org
1. Being triggered by another sync/event-base is the simplest case I can think of. So if you have `foo`, `bar` and `baz` and something like `foo.begin+M` for `bar` and `bar.begin-N` for `baz`. Also note that any `beginEvent` dispatched for an element can have a time stamp in the past. I guess some systems could perhaps also have some latency in event dispatch and use the time the event is dispatched as the event-base time, and not the time is received (and resolved). 2. No it isn't. 3. You can probably use a `%` operator (or similar) to implement it. 4. The first sentence basically says that if the element would end before 'current time' (offset magnitude is greater than the active duration) it shouldn't begin (be ignored). The last two define an offset into the interval at which point the 'media' actually begins - you can refer to the example that follows where you get: `mb = REM(ABS(-8), 3) - 0 = 2` -- GitHub Notification of comment by fsoder Please view or discuss this issue at https://github.com/w3c/svgwg/issues/838#issuecomment-821026686 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Friday, 16 April 2021 08:51:58 UTC