-
Notifications
You must be signed in to change notification settings - Fork 49
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
Detached elements node list is not populated when elements are fetched #233
Comments
Thanks so much for reporting this, and providing these details. I had not yet updated my Stable Edge, so I was able to test with 121 and confirmed that it worked fine there. So you've discovered a 122 regression that, unfortunately, went through our release process undetected. I'll mark this up for the team to investigate quickly. |
Same issue with Version 122.0.2365.80 (Official build) (x86_64) MacOS. Any updates? |
No updates to share at this stage yet, but we're working on it. |
@captainbrosset till then any alternative that we can try? |
Hello, still no update on this issue? Thanks in advance. |
No update to share yet on this. I'll get back to you all as soon as I hear more. |
this would also be helpful for us to have working again. |
Hello, still no update on this issue? |
Hi @TaranTwomey and @Chrisyjs - this issue has been fixed in Edge 126. We don't currently plan to back-port this into 124 or 125 given our current release schedule. Edge 126 is currently in Canary and Dev channels, which you can download here: https://www.microsoftedgeinsider.com/ Thanks! |
@robpaveza this work for me after update! Love this tool thanks so much ❤️ |
This is great, thank you for confirming that the feature is now working for you. |
Homie. Any update about my issue? Waiting for response. Thanks you
|
Homie. Any update about my issue? Waiting for response. Thanks you
|
Recently I have been making great use of the 'Detached Elements' tool that Edge DevTools provides, however I noticed after a recent upgrade to the latest versions of Edge that it has stopped populating the Nodes list when collecting.
This issue appears to affect even the latest Canary, as well as the latest stable 122 version (122.0.2365.63) for 64-bit Windows 10. A coworker of mine who is also using the tool is still running 121.0.2277.128 and the tool appears to function correctly. I am currently unable to downgrade my version of edge, so I cannot test this precisly, but if I am able to downgrade, I will update this issue.
Reproduction:
Load the demo page from microsoftedge.github.io/Demos/detached-elements/
Following the same steps from the demo, generate traffic using the 'fast traffic' button.
Generated Traffic, before tool is run
Switch to room 2.
Run the detached elements tool by clicking 'get detached elements'.
Switch Room, collect detached elements
Note that the count in the top right of the tool has updated to show the number of detached elements, but the node list is not populated
This issue appears to affect the latest Canary as well (124.0.2435.0 canary (64-bit)).
AB#49247073
The text was updated successfully, but these errors were encountered: