-
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
In Edge-DevTools, I can't enable/disable css styles #753
Comments
Hello there, is that in the browser or in the extension? |
Wait, I seem to have found a way to reproduce this problem. And this issue occurs in both browsers and extensions |
Thanks for the reproducing information, we will look into this. |
Hello there, we tried to repro this on our end and we can't see the problem, even with the editing step. What local server are you running? Are there any conversion/build steps that might delay the changes of the CSS? |
All right, I used a VSCode extension named "Live Server" as the server, had no other steps. |
Hello there, it seems there is a compatibilty issue with the live server extension that it reloads the document before our changes are applied. Also see #872 for reference. We will try to reach out to the live server team and see what we can do. |
Nothing else, thanks for your help! And before that, I will try some other ways. |
I would recommend filing an issue on https://github.com/ritwickdey/vscode-live-server/ , @codepo8. Maybe there is also a fix possible on this extension, as live server has wide adoption? |
Would love to, yes. |
Closing this issue now. Our dev team tried reproducing it but couldn't. Let me know if there's still a problem here and we can reopen the issue. |
Environment (please complete the following information):
Describe the bug:
Repro steps:
Expected behavior:
Additional context:
Like this, I disabled background-color, but nothing has changed.
![image](https://user-images.githubusercontent.com/49866401/145612610-1f84605d-7b65-4be1-baa3-d41e87f13312.png)
AB#49009863
The text was updated successfully, but these errors were encountered: