-
Notifications
You must be signed in to change notification settings - Fork 0
fix: change play once from being per timeline, to per trigger #11
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
Open
Arukuen
wants to merge
1
commit into
develop
Choose a base branch
from
fix/5-play-once-multiple-trigger
base: develop
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🧩 Analysis chain
🏁 Script executed:
Repository: gambitph/Interactions
Length of output: 10296
🏁 Script executed:
Repository: gambitph/Interactions
Length of output: 4174
🏁 Script executed:
Repository: gambitph/Interactions
Length of output: 2272
🏁 Script executed:
Repository: gambitph/Interactions
Length of output: 2834
WeakSet operations will throw TypeError if
getCurrentTrigger()returns undefined.WeakSet only accepts objects as values; passing primitives or non-objects like undefined will result in a TypeError. The
getCurrentTrigger()method (src/frontend/scripts/class-interaction.js:114) can return undefined when_currentTriggeris undefined andtriggerElementsis empty or falsy.In class-timeline.js:48, the WeakSet
.has()check only executes in frontend mode withonceOnlyenabled, but line 53's.add()call executes unconditionally. IfcurrentTriggeris undefined, line 53 will throw a TypeError regardless of the frontend mode or timeline configuration, crashing the interaction.Additionally, confirm that non-page interactions without defined triggers should always have at least a fallback trigger element to avoid this edge case entirely.