Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fix SMIL interval restarting #19446

Merged
merged 1 commit into from Oct 1, 2019

Conversation

chromium-wpt-export-bot
Copy link
Collaborator

@chromium-wpt-export-bot chromium-wpt-export-bot commented Oct 1, 2019

When an interval restarts we won't necessarily get a new interval, but
just adjust the current interval (which could then potentially end).
Change CheckAndUpdateInterval(...) to reflect this, and narrow the
restart criteria in UpdateActiveState(...).
UpdateActiveState(...) was also only checking for
"inactive" -> "active/frozen" transitions to 'begin', but we need to
check for transitions from "frozen" as well.
Also re-order the check for 'end' so that it is before the one 'begin'.
This will mean that events should get dispatched like:

'begin', 'end', 'begin' and 'end'

when we encounter a restart (like in the testcase),
rather than as previously:

'begin', 'begin', 'end' and 'end'.

Bug: 998526
Change-Id: I56b2391fdcc22f3a22332d6eeb6aa469225497f6
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1821922
Commit-Queue: Fredrik Söderquist <fs@opera.com>
Reviewed-by: Stephen Chenney <schenney@chromium.org>
Cr-Commit-Position: refs/heads/master@{#701710}

Copy link
Collaborator

@wpt-pr-bot wpt-pr-bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Already reviewed downstream.

When an interval restarts we won't necessarily get a new interval, but
just adjust the current interval (which could then potentially end).
Change CheckAndUpdateInterval(...) to reflect this, and narrow the
restart criteria in UpdateActiveState(...).
UpdateActiveState(...) was also only checking for
"inactive" -> "active/frozen" transitions to 'begin', but we need to
check for transitions from "frozen" as well.
Also re-order the check for 'end' so that it is before the one 'begin'.
This will mean that events should get dispatched like:

  'begin', 'end', 'begin' and 'end'

when we encounter a restart (like in the testcase),
rather than as previously:

  'begin', 'begin', 'end' and 'end'.

Bug: 998526
Change-Id: I56b2391fdcc22f3a22332d6eeb6aa469225497f6
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1821922
Commit-Queue: Fredrik Söderquist <fs@opera.com>
Reviewed-by: Stephen Chenney <schenney@chromium.org>
Cr-Commit-Position: refs/heads/master@{#701710}
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants