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

Audio atom media-id varies across page renders #13021

Open
arelra opened this issue Dec 17, 2024 · 0 comments
Open

Audio atom media-id varies across page renders #13021

arelra opened this issue Dec 17, 2024 · 0 comments
Assignees
Labels
Milestone

Comments

@arelra
Copy link
Member

arelra commented Dec 17, 2024

Reported by @SHession

There seems to be an issue where the provided media ID can vary on page loads, which I suspect is the cause of the issue. As an example, on this page, I have seen several distinct values for the data-media-id on the audio element. This means we don't have a way to aggregate all the events for a single audio element because we don't have a consistent identifier.

Possible issue using elementId here which does change on every render from Frontend.

On a quick look it seems we are setting mediaId property to the elementId which is a value set by Frontend that changes on every render.

mediaId: audioBlockElement.elementId,

Chat thread here: https://chat.google.com/room/AAAAG9rU0m0/bQ8Zen2OIdU/bQ8Zen2OIdU?cls=10

@arelra arelra added this to WebX Team Dec 17, 2024
@arelra arelra converted this from a draft issue Dec 17, 2024
@arelra arelra added this to the Requests milestone Dec 17, 2024
@arelra arelra changed the title Audio atom media-id is varying across page renders Audio atom media-id varies across page renders Dec 18, 2024
@arelra arelra moved this from This Sprint to In Progress in WebX Team Dec 19, 2024
@arelra arelra self-assigned this Dec 19, 2024
@shesah shesah added the Bug label Dec 19, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
Status: In Progress
Development

No branches or pull requests

2 participants