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

[cleanup] Remove unneeded child-attached listener that refreshes raycaster objects #721

Merged

Conversation

vincentfretin
Copy link
Contributor

Remove child-attached listener that refreshes raycaster objects.
I really don't see why this code is there. It was introduced in 63e2e1a
Around that time aframevr/aframe@a463d64 changed raycaster component where events were changed from loaded/child-attached/child-detached to object3dset/object3dremove
It doesn't make sense to me to have here child-attached listener but not child-detached.
Removing the listener doesn't change anything, all is still working properly as far as I can see.
I guess it was related to 'a-scene :not([data-aframe-inspector])' selector that was probably not working on all browsers at that time?

And because raycaster component is a dependency of cursor, it's better to set raycaster first and then cursor.

@vincentfretin vincentfretin marked this pull request as draft June 19, 2024 18:08
@vincentfretin vincentfretin marked this pull request as ready for review June 19, 2024 18:15
@vincentfretin vincentfretin changed the title Remove unneeded child-attached listener that refreshes raycaster objects [cleanup] Remove unneeded child-attached listener that refreshes raycaster objects Jul 16, 2024
@dmarcos
Copy link
Member

dmarcos commented Jul 22, 2024

Thanks!

@dmarcos dmarcos merged commit 3a28e20 into aframevr:master Jul 22, 2024
1 check passed
@vincentfretin vincentfretin deleted the remove-child-attached-listener branch July 22, 2024 17:28
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants