-
Notifications
You must be signed in to change notification settings - Fork 249
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
Inspector Icons not visible #1992
Comments
Thanks for filing. Marking this as part of our backlog for investigation. |
@RPossberg I just talked to one of our engineers, and they said it could be a problem with Edge not being up to date on your device. The new version (2.1.4) has already been published and the icons seem to look fine there. It could be that the extension points to a browser version that's out of date and doesn't have the icon fix. Could you please try updating browser versions on your device and see if that resolves the problem? |
Just to add to the previous answer (thank you @captainbrosset 👍) you could also try a different channel. I was able to repro it with the latest insider version and Canary/Dev but works as expected on the latest stable: |
@captainbrosset |
Hi @RPossberg, I'm having a difficult time reproing the issue, this is how it looks for me on the latest vscode insider (stable channel):
|
|
Thank you for your patience in this issue. I am able to repro the bug, my initial investigation currently points that this is an issue affecting only Edge 122+ versions (Beta, Dev and Canary). A temporary workaround is to select the stable (121) channel from the extension settings. We will investigate more and come back with a fix. Thanks for reporting this |
+1 to say I am seeing this issue with the following specs: MacOS: 2016 M1 Max Sonoma 14.3.1 |
Same issue Version: 1.86.2 (user setup) Edge: |
Same. Thanks Version: 1.86.2 (system setup) Edge for Business: |
Same issue vscode Microsoft Edge Developer Tools for Visual Studio Code Microsoft Edge |
Ditto. And I think v122 is now stable since selecting "Stable" channel in the extension settings doesn't workaround the bug anymore. macOS Sonoma 14.3.1 VS Code Version: 1.87.0 (Universal) |
Hi everyone, Thank you the reports, the Devtools team is investigating the issue and we will put out a fix for this soon. |
We just released v2.1.5 which should address this issue. |
Environment (please complete the following information):
OS (Windows 11 Pro 23H2): Build 22635.3139
Extension version (Insiders v2.1.4):
The extension version can be found by hovering or selecting "Microsoft Edge Tools for VS Code" in the VS Code Extensions Marketplace panel.
Describe the bug:
The icons used to navigate the tools are not displaying and cannot be read unless hovering the mouse.
Repro steps:
The error has been occurring when opening Edge Dev Tools in VS Code Insiders Edition since even before todays update. When opening in VS Code, the tool window icons work and are visible with no issue.
Expected behavior:
To work as is it does in the standard release.
Additional context:
See attached comparison screen shots
![Screenshot 2024-02-01 181013](https://private-user-images.githubusercontent.com/122515790/301705745-01b907d1-7600-4dcf-a9ac-d947aae940bd.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3MjMyMTY3MjQsIm5iZiI6MTcyMzIxNjQyNCwicGF0aCI6Ii8xMjI1MTU3OTAvMzAxNzA1NzQ1LTAxYjkwN2QxLTc2MDAtNGRjZi1hOWFjLWQ5NDdhYWU5NDBiZC5wbmc_WC1BbXotQWxnb3JpdGhtPUFXUzQtSE1BQy1TSEEyNTYmWC1BbXotQ3JlZGVudGlhbD1BS0lBVkNPRFlMU0E1M1BRSzRaQSUyRjIwMjQwODA5JTJGdXMtZWFzdC0xJTJGczMlMkZhd3M0X3JlcXVlc3QmWC1BbXotRGF0ZT0yMDI0MDgwOVQxNTEzNDRaJlgtQW16LUV4cGlyZXM9MzAwJlgtQW16LVNpZ25hdHVyZT1iNThhYWQ0MjkyYmI1ZDliOWE2MTM1NTlhMGVlYzVmZWQ1ZGIzOTZkZDRiNjgwOThjNzc4NWExYTA2MWJhYmRmJlgtQW16LVNpZ25lZEhlYWRlcnM9aG9zdCZhY3Rvcl9pZD0wJmtleV9pZD0wJnJlcG9faWQ9MCJ9.qs4Sk3BQ40vYHIfeH3Ms1okJJO4KhbezWxxvQeuX5NA)
![Screenshot 2024-02-01 192300](https://private-user-images.githubusercontent.com/122515790/301706488-6613bc5f-3c85-458b-a652-97caf5b84f58.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3MjMyMTY3MjQsIm5iZiI6MTcyMzIxNjQyNCwicGF0aCI6Ii8xMjI1MTU3OTAvMzAxNzA2NDg4LTY2MTNiYzVmLTNjODUtNDU4Yi1hNjUyLTk3Y2FmNWI4NGY1OC5wbmc_WC1BbXotQWxnb3JpdGhtPUFXUzQtSE1BQy1TSEEyNTYmWC1BbXotQ3JlZGVudGlhbD1BS0lBVkNPRFlMU0E1M1BRSzRaQSUyRjIwMjQwODA5JTJGdXMtZWFzdC0xJTJGczMlMkZhd3M0X3JlcXVlc3QmWC1BbXotRGF0ZT0yMDI0MDgwOVQxNTEzNDRaJlgtQW16LUV4cGlyZXM9MzAwJlgtQW16LVNpZ25hdHVyZT1mMjk0MWRmMDc3NzZlZGM2MWU3NDEzMmZiYTUyNzExZWRiYzgxZGY1N2NhYTNjMmE2YzUxNzg5OWRjOTU3OTM1JlgtQW16LVNpZ25lZEhlYWRlcnM9aG9zdCZhY3Rvcl9pZD0wJmtleV9pZD0wJnJlcG9faWQ9MCJ9.lGmpZCZudyL0xcd0l_mP1ElSmEVleKDTiHJqZPsTcH4)
The text was updated successfully, but these errors were encountered: