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

Always syncing CSS changes in the Styles pane #247

Open
royalone opened this issue Apr 15, 2024 · 6 comments
Open

Always syncing CSS changes in the Styles pane #247

royalone opened this issue Apr 15, 2024 · 6 comments
Labels
bug Something isn't working tracked This issue is now tracked on our internal backlog

Comments

@royalone
Copy link

royalone commented Apr 15, 2024

In the styles tab in the elements tool, changes I make to the CSS are synced and saving to file even though I have made sure the Sync CSS changes in the Styles pane experimental feature flag is disabled. The documentation for this provides no information but I assume it means whether or not these changes get saved to disk.

I do not want to sync my CSS changes as I build them with a .LESS file, and having the .CSS and .LESS not the same can lead to confusion. Even without the .LESS files, I doubt I'd want the feature enabled, as I really just use the styles tab for experimenting with what looks good before I 'commit' to my codebase

This behaviour of syncing to disk is also present for any file I edit in the sources tab (.js files for example) which I probably would disable too given the choice, but I'm never really editing source files from within Devtools.
I have linked my working directory to Devtools.

Version 123.0.2420.97 (Official build) (64-bit)
Thank you

AB#50931662

@royalone royalone added the bug Something isn't working label Apr 15, 2024
@captainbrosset
Copy link
Contributor

Are you using DevTools from within VSCode, by using our Edge DevTools VSCode extension? If so, then you might need to disable "CSS mirroring" as explained here: https://learn.microsoft.com/en-gb/microsoft-edge/visual-studio-code/microsoft-edge-devtools-extension/css-mirror-editing-styles-tab

@captainbrosset captainbrosset added the more info needed We need more information before we can act on this issue label Apr 15, 2024
@royalone
Copy link
Author

I was not using edge from inside VSCode, but I did have the extension installed. I've since uninstalled it and rebooted VSCode and Edge but my all my changes (.CSS and everything else) are all still syncing.

@royalone
Copy link
Author

royalone commented Apr 16, 2024

For now I'm just going to unlink my workspace, as the only reason I want them linked is to be able to open my files in VSCode through the Devtools console or elements tab etc. But since that isn't working for me right now, I'll just unlink.

This is not ideal though, because I can no longer hot reload my styles by altering my files, I have to refresh the page again for them to take effect.

@royalone
Copy link
Author

Bump

@carenrose
Copy link

I do not have VSCode installed at all - I'm having this issue.

"Sync CSS changes in the Styles pane" is unchecked.

If I remove the folder from the "Workspace", changes made to the file directly in another application (Visual Studio, Notepad++, etc) are not synced at all, meaning I have to refresh the page for every change made - which is not what I want.

Previously, there was a setting that allowed changes made outside the browser to be applied as soon as the file was saved, but kept changes made in DevTools from being written to file. I'm not sure if that's the "Sync CSS changes in the Styles pane" and it is broken, or if there's another setting somewhere else that isn't intuitively named.

@captainbrosset captainbrosset added tracked This issue is now tracked on our internal backlog and removed more info needed We need more information before we can act on this issue labels May 15, 2024
@captainbrosset
Copy link
Contributor

Sorry about the delay here. I've marked this as tracked for our dev team to triage/prioritize it on their backlog.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working tracked This issue is now tracked on our internal backlog
Projects
None yet
Development

No branches or pull requests

3 participants