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

Invisible breakpoint in DevTools's Sources tab #293

Open
datvm opened this issue Nov 18, 2024 · 7 comments
Open

Invisible breakpoint in DevTools's Sources tab #293

datvm opened this issue Nov 18, 2024 · 7 comments
Labels
bug Something isn't working

Comments

@datvm
Copy link

datvm commented Nov 18, 2024

All of a sudden all breakpoints in DevTools are invisible. They still function normally but I cannot see the breakpoint symbol and the line highlight:

Recording.2024-11-18.220943.mp4

image

@datvm datvm added the bug Something isn't working label Nov 18, 2024
@leahmsft
Copy link

Thank you for reporting. This is a known bug, and the engineering team is working on a fix.

Can you provide details on what browser version you're seeing the bug?

@datvm
Copy link
Author

datvm commented Nov 18, 2024

@leahmsft it's Version 131.0.2903.51 (Official build) (64-bit)

@leahmsft
Copy link

This should already be fixed in version 131. Are you seeing the issue in both light and dark theme?

@datvm
Copy link
Author

datvm commented Nov 19, 2024

@leahmsft interesting, if I switch to Dark theme, the problem goes away until I restart Edge.

  • Start in Dark: problem never happens.
  • Start in Light: happen until I switch to Dark.
    • After that, no matter if I switch back to Light, the problem does not happen again until I restart Edge in Light theme

Basically once it enters Dark theme, the problem goes away until restart.

Edit: clarify.

@Neo-Stark
Copy link

The same issue and the same workaround working here.

@gryno
Copy link

gryno commented Nov 19, 2024

I get the same bug too, and the workaround described here works as others described. (Interesting that it just started happening today and that others have just found this issue very recently too.)

@leahmsft
Copy link

Thank you for the repro steps @datvm! I can now see the same bug following your steps. I'll share this back with the engineering team to take a look. I'll update you all once we land a fix.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

4 participants