Is there any way to open local file directly from 'Elements > Styles' tab in Chrome devtools?I want to edit my sass file from Chrome dev tool from element tab, is that possible?How do I view events fired on an element in Chrome DevTools?Emmet in Chrome devtools' sources tab?Chrome DevTools save CSS changes directly to SASS fileChrome DevTools: SASS source file doesn't get saved on diskChrome Devtools: If I map my local resources to network resources my source map links in the style inspector disappearsHow to organize local folders in Chrome DevTools workspace?Live SASS in Chrome DevTools troubleshooting (mapping lost for one file only)Chrome DevTools points to wrong sass file in sourcemapChrome DevTools persisting changes via Styles panelChrome devtools save changed file path
Why does the U.S. tolerate foreign influence from Saudi Arabia and Israel on its domestic policies while not tolerating that from China or Russia?
Single word for "refusing to move to next activity unless present one is completed."
Simple interepretation problem regarding Polynomial Hierarchy?
Was I subtly told to resign?
Why are Hobbits so fond of mushrooms?
Using Newton's shell theorem to accelerate a spaceship
How to tell someone I'd like to become friends without causing them to them think I'm romantically interested in them?
RPI3B+: What are the four components below the HDMI connector called?
Are there any sports for which the world's best player is female?
Matchmaker, Matchmaker, make me a match
If your plane is out-of-control, why does military training instruct releasing the joystick to neutralize controls?
Need help identifying planes, near Toronto
Why does it output Integers instead of letters?
How can one write good dialogue in a story without sounding wooden?
Would dual wielding daggers be a viable choice for a covert bodyguard?
Optimization terminology: "Exact" v. "Approximate"
Reverse dots and boxes, swastika edition
Are randomly-generated passwords starting with "a" less secure?
Storming Area 51
Why didn't Thanos kill all the Dwarves on Nidavellir?
How to memorize multiple pieces?
Why did Harry Potter get a bedroom?
Generating random numbers that keep a minimum distance
Multiple DUI convictions 12 years ago. Do I disclose if I know they will do a background check?
Is there any way to open local file directly from 'Elements > Styles' tab in Chrome devtools?
I want to edit my sass file from Chrome dev tool from element tab, is that possible?How do I view events fired on an element in Chrome DevTools?Emmet in Chrome devtools' sources tab?Chrome DevTools save CSS changes directly to SASS fileChrome DevTools: SASS source file doesn't get saved on diskChrome Devtools: If I map my local resources to network resources my source map links in the style inspector disappearsHow to organize local folders in Chrome DevTools workspace?Live SASS in Chrome DevTools troubleshooting (mapping lost for one file only)Chrome DevTools points to wrong sass file in sourcemapChrome DevTools persisting changes via Styles panelChrome devtools save changed file path
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty margin-bottom:0;
I'm using the Chrome devtools persistence feature with browser-sync and sass.
I set a Workspace pointing to my scss folder and I can edit scss files from Chrome and have all css files created correctly, applied to browser real-time and saved in hard drive.
However when I select an element on the Elements > Styles tab and make some changes, the changed file is the http://localhost:3000... one so changes are not kept. Then I still have to find the local file in the Sources tab to copy these changes.
I'm not sure if this is the best we can get but if we could either open the local file directly from the Elements > Style tab instead of the http://localhost:3000... file or somehow automatically copy any changes in the http://localhost:3000... file to local file the workflow would be even easier and faster.
Does any one knows how to accomplish that, even using some app/extension?
UPDATE:
From Rohit answer I found that if I turn off css source maps in devtools settings then it is correctly synced, showing the green circle on the Elements > Style and keep my changes, although it still pointing to http://localhost:3000...style.css file.
However then it only changes this file, not the specific partials/*.scss file and if I run sass compiler it overrides the css with the old code.
With the css source maps on Chrome finds my partial scss correctly but doesn't show the green circle so it's not synced and doesn't keep changes.
The problem seems to be with syncing scss files instead of css.
I was trying with a Workspace pointing to my root scss folder, also tried pointing it to the direct parent of the file beeing edited and still not syncing corretly.
css sass
google-chrome-devtools browser-sync asked Mar 26 at 2:35
GoblinGoblin
235 bronze badges
add a comment |
I'm using the Chrome devtools persistence feature with browser-sync and sass.
I set a Workspace pointing to my scss folder and I can edit scss files from Chrome and have all css files created correctly, applied to browser real-time and saved in hard drive.
However when I select an element on the Elements > Styles tab and make some changes, the changed file is the http://localhost:3000... one so changes are not kept. Then I still have to find the local file in the Sources tab to copy these changes.
I'm not sure if this is the best we can get but if we could either open the local file directly from the Elements > Style tab instead of the http://localhost:3000... file or somehow automatically copy any changes in the http://localhost:3000... file to local file the workflow would be even easier and faster.
Does any one knows how to accomplish that, even using some app/extension?
UPDATE:
From Rohit answer I found that if I turn off css source maps in devtools settings then it is correctly synced, showing the green circle on the Elements > Style and keep my changes, although it still pointing to http://localhost:3000...style.css file.
However then it only changes this file, not the specific partials/*.scss file and if I run sass compiler it overrides the css with the old code.
With the css source maps on Chrome finds my partial scss correctly but doesn't show the green circle so it's not synced and doesn't keep changes.
The problem seems to be with syncing scss files instead of css.
I was trying with a Workspace pointing to my root scss folder, also tried pointing it to the direct parent of the file beeing edited and still not syncing corretly.
css sass
google-chrome-devtools browser-sync asked Mar 26 at 2:35
GoblinGoblin
235 bronze badges
add a comment |
I'm using the Chrome devtools persistence feature with browser-sync and sass.
I set a Workspace pointing to my scss folder and I can edit scss files from Chrome and have all css files created correctly, applied to browser real-time and saved in hard drive.
However when I select an element on the Elements > Styles tab and make some changes, the changed file is the http://localhost:3000... one so changes are not kept. Then I still have to find the local file in the Sources tab to copy these changes.
I'm not sure if this is the best we can get but if we could either open the local file directly from the Elements > Style tab instead of the http://localhost:3000... file or somehow automatically copy any changes in the http://localhost:3000... file to local file the workflow would be even easier and faster.
Does any one knows how to accomplish that, even using some app/extension?
UPDATE:
From Rohit answer I found that if I turn off css source maps in devtools settings then it is correctly synced, showing the green circle on the Elements > Style and keep my changes, although it still pointing to http://localhost:3000...style.css file.
However then it only changes this file, not the specific partials/*.scss file and if I run sass compiler it overrides the css with the old code.
With the css source maps on Chrome finds my partial scss correctly but doesn't show the green circle so it's not synced and doesn't keep changes.
The problem seems to be with syncing scss files instead of css.
I was trying with a Workspace pointing to my root scss folder, also tried pointing it to the direct parent of the file beeing edited and still not syncing corretly.
css sass
google-chrome-devtools browser-sync asked Mar 26 at 2:35
GoblinGoblin
235 bronze badges
I'm using the Chrome devtools persistence feature with browser-sync and sass.
I set a Workspace pointing to my scss folder and I can edit scss files from Chrome and have all css files created correctly, applied to browser real-time and saved in hard drive.
However when I select an element on the Elements > Styles tab and make some changes, the changed file is the http://localhost:3000... one so changes are not kept. Then I still have to find the local file in the Sources tab to copy these changes.
I'm not sure if this is the best we can get but if we could either open the local file directly from the Elements > Style tab instead of the http://localhost:3000... file or somehow automatically copy any changes in the http://localhost:3000... file to local file the workflow would be even easier and faster.
Does any one knows how to accomplish that, even using some app/extension?
UPDATE:
From Rohit answer I found that if I turn off css source maps in devtools settings then it is correctly synced, showing the green circle on the Elements > Style and keep my changes, although it still pointing to http://localhost:3000...style.css file.
However then it only changes this file, not the specific partials/*.scss file and if I run sass compiler it overrides the css with the old code.
With the css source maps on Chrome finds my partial scss correctly but doesn't show the green circle so it's not synced and doesn't keep changes.
The problem seems to be with syncing scss files instead of css.
I was trying with a Workspace pointing to my root scss folder, also tried pointing it to the direct parent of the file beeing edited and still not syncing corretly.
css sass
google-chrome-devtools browser-sync css sass
google-chrome-devtools browser-sync asked Mar 26 at 2:35
GoblinGoblin
235 bronze badges
asked Mar 26 at 2:35
GoblinGoblin
235 bronze badges
edited Mar 26 at 17:43
Goblin
asked Mar 26 at 2:35
GoblinGoblin
235 bronze badges
asked Mar 26 at 2:35
GoblinGoblin
235 bronze badges
asked Mar 26 at 2:35
GoblinGoblin
235 bronze badges
235 bronze badges
add a comment |
add a comment |
2 Answers
2
active
oldest
votes
This is a shot in the dark but,I beleive if you add the parent folder of the files you are working on from Devtools > Sources Tab > Filesystem tab > Add folder to workspace.
Like so :
Then navigate to your folder, and add reload the page. After reloading if you see green
like so:
It means it is synced and will update without you going to the sources tab.
answered Mar 26 at 5:08
Rohit KumarRohit Kumar
2312 silver badges20 bronze badges
if I turn off css source maps in devtools settings it get the green circle and although it still pointing to localhost:3000 the changes are kept. However then it only changes my style.css not the specific partial scss and if I run sass compiler it overrides the css with the old code. With the source maps on Chrome finds my partial scss correctly but doesn't keep changes.
– Goblin
Mar 26 at 5:52
Yes, you can only change non-compiling css like css. But, as you know sass needs to be compiled before it can be used, and chrome does not provide a feature to edit a sass file and then to create the css from it and then render it as of now. So, you may have work around with css files only. This may help you though stackoverflow.com/questions/46360983/…
– Rohit Kumar
Mar 26 at 6:04
Yes, I know but Netbeans is automatically compiling sass on any changes in scss folder. So I just need to be able to sync the scss as I could do with css. Changing the localhost file on devtools would render right away on screen, then if files are synced the scss will change on disk and Netbeans will compile sass. I guess like this I wouldn't need browser-sync.
– Goblin
Mar 26 at 6:48
The question you shared seems to be about the same thing, but Live SASS option is not available in the experiments tab anymore. Don't know if it's stable and running or was droped.
– Goblin
Mar 26 at 6:53
Yes that was what I found closest to your query
– Rohit Kumar
Mar 26 at 8:37
add a comment |
Adding the root of my project to the Workspace synced scss files correctly. Now when I click an element on the Element > Styles tab, Quick source opens the right file at the right scss rule but doesn't follow my changes in the Element > Styles tab (as it does using pure css) and I still need to copy changes to Quick source or edit there directly, save and wait sass compilation to apply changes on screen.
The workflow is much easier now but I'm not choosing this as the correct anwser because is not "as live as css" yet and maybe someone knows how to do this final step.
PS: browser-sync is not needed in this setup, just something to compile sass and Chrome apply changes automatically.
answered Mar 26 at 20:35
GoblinGoblin
235 bronze badges
add a comment |
Your Answer
StackExchange.ifUsing("editor", function ()
StackExchange.using("externalEditor", function ()
StackExchange.using("snippets", function ()
StackExchange.snippets.init();
);
);
, "code-snippets");
StackExchange.ready(function()
var channelOptions =
tags: "".split(" "),
id: "1"
;
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function()
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled)
StackExchange.using("snippets", function()
createEditor();
);
else
createEditor();
);
function createEditor()
StackExchange.prepareEditor(
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader:
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
,
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
);
);
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f55349056%2fis-there-any-way-to-open-local-file-directly-from-elements-styles-tab-in-chr%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
2 Answers
2
active
oldest
votes
2 Answers
2
active
oldest
votes
active
oldest
votes
active
oldest
votes
This is a shot in the dark but,I beleive if you add the parent folder of the files you are working on from Devtools > Sources Tab > Filesystem tab > Add folder to workspace.
Like so :
Then navigate to your folder, and add reload the page. After reloading if you see green
like so:
It means it is synced and will update without you going to the sources tab.
answered Mar 26 at 5:08
Rohit KumarRohit Kumar
2312 silver badges20 bronze badges
if I turn off css source maps in devtools settings it get the green circle and although it still pointing to localhost:3000 the changes are kept. However then it only changes my style.css not the specific partial scss and if I run sass compiler it overrides the css with the old code. With the source maps on Chrome finds my partial scss correctly but doesn't keep changes.
– Goblin
Mar 26 at 5:52
Yes, you can only change non-compiling css like css. But, as you know sass needs to be compiled before it can be used, and chrome does not provide a feature to edit a sass file and then to create the css from it and then render it as of now. So, you may have work around with css files only. This may help you though stackoverflow.com/questions/46360983/…
– Rohit Kumar
Mar 26 at 6:04
Yes, I know but Netbeans is automatically compiling sass on any changes in scss folder. So I just need to be able to sync the scss as I could do with css. Changing the localhost file on devtools would render right away on screen, then if files are synced the scss will change on disk and Netbeans will compile sass. I guess like this I wouldn't need browser-sync.
– Goblin
Mar 26 at 6:48
The question you shared seems to be about the same thing, but Live SASS option is not available in the experiments tab anymore. Don't know if it's stable and running or was droped.
– Goblin
Mar 26 at 6:53
Yes that was what I found closest to your query
– Rohit Kumar
Mar 26 at 8:37
add a comment |
This is a shot in the dark but,I beleive if you add the parent folder of the files you are working on from Devtools > Sources Tab > Filesystem tab > Add folder to workspace.
Like so :
Then navigate to your folder, and add reload the page. After reloading if you see green
like so:
It means it is synced and will update without you going to the sources tab.
answered Mar 26 at 5:08
Rohit KumarRohit Kumar
2312 silver badges20 bronze badges
if I turn off css source maps in devtools settings it get the green circle and although it still pointing to localhost:3000 the changes are kept. However then it only changes my style.css not the specific partial scss and if I run sass compiler it overrides the css with the old code. With the source maps on Chrome finds my partial scss correctly but doesn't keep changes.
– Goblin
Mar 26 at 5:52
Yes, you can only change non-compiling css like css. But, as you know sass needs to be compiled before it can be used, and chrome does not provide a feature to edit a sass file and then to create the css from it and then render it as of now. So, you may have work around with css files only. This may help you though stackoverflow.com/questions/46360983/…
– Rohit Kumar
Mar 26 at 6:04
Yes, I know but Netbeans is automatically compiling sass on any changes in scss folder. So I just need to be able to sync the scss as I could do with css. Changing the localhost file on devtools would render right away on screen, then if files are synced the scss will change on disk and Netbeans will compile sass. I guess like this I wouldn't need browser-sync.
– Goblin
Mar 26 at 6:48
The question you shared seems to be about the same thing, but Live SASS option is not available in the experiments tab anymore. Don't know if it's stable and running or was droped.
– Goblin
Mar 26 at 6:53
Yes that was what I found closest to your query
– Rohit Kumar
Mar 26 at 8:37
add a comment |
This is a shot in the dark but,I beleive if you add the parent folder of the files you are working on from Devtools > Sources Tab > Filesystem tab > Add folder to workspace.
Like so :
Then navigate to your folder, and add reload the page. After reloading if you see green
like so:
It means it is synced and will update without you going to the sources tab.
answered Mar 26 at 5:08
Rohit KumarRohit Kumar
2312 silver badges20 bronze badges
This is a shot in the dark but,I beleive if you add the parent folder of the files you are working on from Devtools > Sources Tab > Filesystem tab > Add folder to workspace.
Like so :
Then navigate to your folder, and add reload the page. After reloading if you see green
like so:
It means it is synced and will update without you going to the sources tab.
answered Mar 26 at 5:08
Rohit KumarRohit Kumar
2312 silver badges20 bronze badges
answered Mar 26 at 5:08
Rohit KumarRohit Kumar
2312 silver badges20 bronze badges
answered Mar 26 at 5:08
Rohit KumarRohit Kumar
2312 silver badges20 bronze badges
answered Mar 26 at 5:08
Rohit KumarRohit Kumar
2312 silver badges20 bronze badges
2312 silver badges20 bronze badges
if I turn off css source maps in devtools settings it get the green circle and although it still pointing to localhost:3000 the changes are kept. However then it only changes my style.css not the specific partial scss and if I run sass compiler it overrides the css with the old code. With the source maps on Chrome finds my partial scss correctly but doesn't keep changes.
– Goblin
Mar 26 at 5:52
Yes, you can only change non-compiling css like css. But, as you know sass needs to be compiled before it can be used, and chrome does not provide a feature to edit a sass file and then to create the css from it and then render it as of now. So, you may have work around with css files only. This may help you though stackoverflow.com/questions/46360983/…
– Rohit Kumar
Mar 26 at 6:04
Yes, I know but Netbeans is automatically compiling sass on any changes in scss folder. So I just need to be able to sync the scss as I could do with css. Changing the localhost file on devtools would render right away on screen, then if files are synced the scss will change on disk and Netbeans will compile sass. I guess like this I wouldn't need browser-sync.
– Goblin
Mar 26 at 6:48
The question you shared seems to be about the same thing, but Live SASS option is not available in the experiments tab anymore. Don't know if it's stable and running or was droped.
– Goblin
Mar 26 at 6:53
Yes that was what I found closest to your query
– Rohit Kumar
Mar 26 at 8:37
add a comment |
if I turn off css source maps in devtools settings it get the green circle and although it still pointing to localhost:3000 the changes are kept. However then it only changes my style.css not the specific partial scss and if I run sass compiler it overrides the css with the old code. With the source maps on Chrome finds my partial scss correctly but doesn't keep changes.
– Goblin
Mar 26 at 5:52
Yes, you can only change non-compiling css like css. But, as you know sass needs to be compiled before it can be used, and chrome does not provide a feature to edit a sass file and then to create the css from it and then render it as of now. So, you may have work around with css files only. This may help you though stackoverflow.com/questions/46360983/…
– Rohit Kumar
Mar 26 at 6:04
Yes, I know but Netbeans is automatically compiling sass on any changes in scss folder. So I just need to be able to sync the scss as I could do with css. Changing the localhost file on devtools would render right away on screen, then if files are synced the scss will change on disk and Netbeans will compile sass. I guess like this I wouldn't need browser-sync.
– Goblin
Mar 26 at 6:48
The question you shared seems to be about the same thing, but Live SASS option is not available in the experiments tab anymore. Don't know if it's stable and running or was droped.
– Goblin
Mar 26 at 6:53
Yes that was what I found closest to your query
– Rohit Kumar
Mar 26 at 8:37
if I turn off css source maps in devtools settings it get the green circle and although it still pointing to localhost:3000 the changes are kept. However then it only changes my style.css not the specific partial scss and if I run sass compiler it overrides the css with the old code. With the source maps on Chrome finds my partial scss correctly but doesn't keep changes.
– Goblin
Mar 26 at 5:52
if I turn off css source maps in devtools settings it get the green circle and although it still pointing to localhost:3000 the changes are kept. However then it only changes my style.css not the specific partial scss and if I run sass compiler it overrides the css with the old code. With the source maps on Chrome finds my partial scss correctly but doesn't keep changes.
– Goblin
Mar 26 at 5:52
Yes, you can only change non-compiling css like css. But, as you know sass needs to be compiled before it can be used, and chrome does not provide a feature to edit a sass file and then to create the css from it and then render it as of now. So, you may have work around with css files only. This may help you though stackoverflow.com/questions/46360983/…
– Rohit Kumar
Mar 26 at 6:04
Yes, you can only change non-compiling css like css. But, as you know sass needs to be compiled before it can be used, and chrome does not provide a feature to edit a sass file and then to create the css from it and then render it as of now. So, you may have work around with css files only. This may help you though stackoverflow.com/questions/46360983/…
– Rohit Kumar
Mar 26 at 6:04
Yes, I know but Netbeans is automatically compiling sass on any changes in scss folder. So I just need to be able to sync the scss as I could do with css. Changing the localhost file on devtools would render right away on screen, then if files are synced the scss will change on disk and Netbeans will compile sass. I guess like this I wouldn't need browser-sync.
– Goblin
Mar 26 at 6:48
Yes, I know but Netbeans is automatically compiling sass on any changes in scss folder. So I just need to be able to sync the scss as I could do with css. Changing the localhost file on devtools would render right away on screen, then if files are synced the scss will change on disk and Netbeans will compile sass. I guess like this I wouldn't need browser-sync.
– Goblin
Mar 26 at 6:48
The question you shared seems to be about the same thing, but Live SASS option is not available in the experiments tab anymore. Don't know if it's stable and running or was droped.
– Goblin
Mar 26 at 6:53
The question you shared seems to be about the same thing, but Live SASS option is not available in the experiments tab anymore. Don't know if it's stable and running or was droped.
– Goblin
Mar 26 at 6:53
Yes that was what I found closest to your query
– Rohit Kumar
Mar 26 at 8:37
Yes that was what I found closest to your query
– Rohit Kumar
Mar 26 at 8:37
add a comment |
Adding the root of my project to the Workspace synced scss files correctly. Now when I click an element on the Element > Styles tab, Quick source opens the right file at the right scss rule but doesn't follow my changes in the Element > Styles tab (as it does using pure css) and I still need to copy changes to Quick source or edit there directly, save and wait sass compilation to apply changes on screen.
The workflow is much easier now but I'm not choosing this as the correct anwser because is not "as live as css" yet and maybe someone knows how to do this final step.
PS: browser-sync is not needed in this setup, just something to compile sass and Chrome apply changes automatically.
answered Mar 26 at 20:35
GoblinGoblin
235 bronze badges
add a comment |
Adding the root of my project to the Workspace synced scss files correctly. Now when I click an element on the Element > Styles tab, Quick source opens the right file at the right scss rule but doesn't follow my changes in the Element > Styles tab (as it does using pure css) and I still need to copy changes to Quick source or edit there directly, save and wait sass compilation to apply changes on screen.
The workflow is much easier now but I'm not choosing this as the correct anwser because is not "as live as css" yet and maybe someone knows how to do this final step.
PS: browser-sync is not needed in this setup, just something to compile sass and Chrome apply changes automatically.
answered Mar 26 at 20:35
GoblinGoblin
235 bronze badges
add a comment |
Adding the root of my project to the Workspace synced scss files correctly. Now when I click an element on the Element > Styles tab, Quick source opens the right file at the right scss rule but doesn't follow my changes in the Element > Styles tab (as it does using pure css) and I still need to copy changes to Quick source or edit there directly, save and wait sass compilation to apply changes on screen.
The workflow is much easier now but I'm not choosing this as the correct anwser because is not "as live as css" yet and maybe someone knows how to do this final step.
PS: browser-sync is not needed in this setup, just something to compile sass and Chrome apply changes automatically.
answered Mar 26 at 20:35
GoblinGoblin
235 bronze badges
Adding the root of my project to the Workspace synced scss files correctly. Now when I click an element on the Element > Styles tab, Quick source opens the right file at the right scss rule but doesn't follow my changes in the Element > Styles tab (as it does using pure css) and I still need to copy changes to Quick source or edit there directly, save and wait sass compilation to apply changes on screen.
The workflow is much easier now but I'm not choosing this as the correct anwser because is not "as live as css" yet and maybe someone knows how to do this final step.
PS: browser-sync is not needed in this setup, just something to compile sass and Chrome apply changes automatically.
answered Mar 26 at 20:35
GoblinGoblin
235 bronze badges
edited Mar 26 at 20:42
answered Mar 26 at 20:35
GoblinGoblin
235 bronze badges
answered Mar 26 at 20:35
GoblinGoblin
235 bronze badges
answered Mar 26 at 20:35
GoblinGoblin
235 bronze badges
235 bronze badges
add a comment |
add a comment |
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f55349056%2fis-there-any-way-to-open-local-file-directly-from-elements-styles-tab-in-chr%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
