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.

Sign up for GitHub

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

Jump to bottom

[BUG] When using Multiple instances of AI only the first instance is correctly reporting ajax events #1655

Closed
MSNev opened this issue Sep 2, 2021 · 1 comment
Closed

[BUG] When using Multiple instances of AI only the first instance is correctly reporting ajax events #1655

MSNev opened this issue Sep 2, 2021 · 1 comment
Assignees
@MSNev
Labels
bug p2 released - NPM
Milestone
2.7.1

Comments

@MSNev
Copy link
Collaborator

MSNev commented Sep 2, 2021 •
edited
Loading

When the Ajax dependencies extension hooks the XMLHttpRequests it tags each instance as being monitored, this is blocking subsequent listeners from attaching and reporting when the ajax requests return.

Specifically, this occurs in the _isMonitoredXhrInstance() within the _instrumentXhr(), fetch doesn't appear to have the same issue -- but needs to be validated

Which causes the code to not listen to the onreadystatechange
@MSNev MSNev self-assigned this Sep 2, 2021
@MSNev MSNev added this to the 2.x.x (Future Release) milestone Oct 5, 2021
MSNev added a commit that referenced this issue Oct 6, 2021
@MSNev
[BUG] When using Multiple instances of AI only the first instance is …
2ddd51f 
…correctly reporting ajax events #1655
MSNev added a commit that referenced this issue Oct 6, 2021
@MSNev
[BUG] When using Multiple instances of AI only the first instance is …
25e8375 
…correctly reporting ajax events #1655 (#1686)
@MSNev MSNev added the fixed - waiting release PR Committed and waiting deployment label Oct 6, 2021
@MSNev MSNev closed this as completed Nov 10, 2021
@github-actions
Copy link

This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Nov 11, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees

@MSNev MSNev

Labels
bug p2 released - NPM
Projects
None yet
Milestone
2.7.1
Development

No branches or pull requests
1 participant
@MSNev