Stop switching sourcefiles, when i edit css styles in sidebar

[Treen]

Hi,

normaly, when i inspect some elemnt with dev tools, it shows this elements css styles in the sidebar. I'm using sass, so next to those styles is a refference to a scss file and line number.

But, when i edit those styles in the sidebar, the sourcefile switches to the compiled output .css file. I'd like it to keep the scss file instead. I'm not editing my code live using dev tools, i'm just using it for debugging and inspecting. 

Below are screens.

When i load page, before i do anything (notice the file and line number refference). This is how i'd like it to be all the time:

After i edit some styles in the sidebar (again, notice the file and line number refference)

Is there any way, to get rid of this "source file switching" thingy?

[Treen]

Anyone?

[Treen]

Bump

[Paul Irish]

Hi Treen,

This bug was fixed a few months back. It hasn't made it to stable yet, but is likely in Chrome Beta.

You can use Canary, Beta, Dev in the meantime until the next stable version of chrome ships. (about a month away)

On Tue, Jun 28, 2016 at 2:47 AM, Treen <l.bob...@gmail.com> wrote:

Bump

--
You received this message because you are subscribed to the Google Groups "Google Chrome Developer Tools" group.
To unsubscribe from this group and stop receiving emails from it, send an email to google-chrome-develo...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/google-chrome-developer-tools/82912498-2092-482f-b88e-17c0919a865e%40googlegroups.com.

For more options, visit https://groups.google.com/d/optout.

[Paul Irish]

My mistake,

We reintroduced the bug unfortunately. It's broken in Canary as well.

Here's the ticket: https://bugs.chromium.org/p/chromium/issues/detail?id=257778#c66

I've added a workaround that should help you in the meantime while we fix this.

[Treen]

Dne čtvrtek 30. června 2016 21:59:08 UTC+2 Paul Irish napsal(a):

My mistake,

We reintroduced the bug unfortunately. It's broken in Canary as well.

Here's the ticket: https://bugs.chromium.org/p/chromium/issues/detail?id=257778#c66

I've added a workaround that should help you in the meantime while we fix this.

That worked.. Thank you very much :)