-
Notifications
You must be signed in to change notification settings - Fork 65
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
Searching for element freezes entire web page [Pixi v4.8.7] #129
Comments
This doesn't happen in the smaller projects i'm testing with, is your project available online? |
Thank you for the quick response! It is not a project I can share publicly, but it may have to do with the fact that the project uses PIXI version 4.8.7. Could using an outdated PIXI version cause incompatibilities with the extension? |
That is possible, we don't have a testsuite that tests different Pixi versions. that is something on my wishlist. |
Understandable, appreciate the heads up. I've updated the ticket to include the pixi version this issue is occurring in. For additional context when a test suite for multiple Pixi versions comes to fruition, a workaround we found for the time being is to search for the element, and the element would appear in the hierarchy, but the page freezes. We click on the element to highlight it on the page, and then we clear the search box and wait for the page to unfreeze. From there, we select the item again and we can work with the Pixi inspector as we normally would. EDIT: For more additional context, this became a problem in the most recent version of the extension that was updated on April 19th, 2024. Prior to that update, we were not experiencing any freezing. |
I have the same freezes problem with my project too. When I try to find element. |
As the title suggests, attempting to search for a specific pixi element in the search bar causes the entire page to freeze up, which can only be rectified by closing the tab and reopening. As I have a heavy webpage with a lot of overlapping elements, it would be unreliable for me to right click the element to pull it up on the inspector, and it would be very inefficient to manually search through the container hierarchy to search for the element.
The text was updated successfully, but these errors were encountered: