S. Robijns
S. Robijns

Reputation: 1599

How to get a summary of your CSS changes in Chrome dev tools?

Is there a way to get a list of the custom CSS changes you applied within the Chrome dev tools?

When you're playing with CSS in the Chrome dev tools to get your web page look right, it would come in handy to easily track the changes you made.

I know about workspaces, but the use case is an Angular 5 app where your CSS is bundled and possibly minified.

To clarify:

Upvotes: 65

Views: 20789

Answers (5)

KyleMit
KyleMit

Reputation: 29889

You can see all changes via the Changes Drawer

Changes Drawer

In Dev Tools, you can locate the Changes Drawer via either:

  • A) Open Command Palette (Ctrl + Shift + P) and type "changes"

    Command Palette > Changes

  • B) Open Drawer (Esc), click on the more options menu (triple dot), and select Changes

    Drawer Menu > Changes

Further Reading

Updates

Upvotes: 56

scoop96
scoop96

Reputation: 11

I know it's "another" subject, but you can try to launch it in some live checker extension in VS Code in order to follow everything...

Upvotes: -1

Obmerk Kronen
Obmerk Kronen

Reputation: 15949

Actually you could do exactly what you want:

Go to Sources > > Local Modifications

Going to the Sources tab, choosing your desired CSS file, and then right click and choose Local modifications will give you a diff style summary of your local changes.

Local CSS modifications in Chrome dev tools

Or - you could just save the changes directly to a local CSS file by mapping that local file so that chrome dev tools will automatically save any change that you made to this CSS file.

Upvotes: 25

Michael Dimmitt
Michael Dimmitt

Reputation: 1054

Well, I learned something new 😯

How to monitor changes to inline styles in console

https://developer.mozilla.org/en-US/docs/Web/API/MutationObserver

references: https://hacks.mozilla.org/2012/05/dom-mutationobserver-reacting-to-dom-changes-without-killing-browser-performance/

const targetNode = document

// Options for the observer (which mutations to observe)
const config = { attributes: true, childList: true, subtree: true };

// Callback function to execute when mutations are observed
const callback = function(mutationsList, observer) {
    // Use traditional 'for loops' for IE 11
    for(let mutation of mutationsList) {
        if (mutation.type === 'childList') {
            console.log('A child node has been added or removed.');
        }
        else if (mutation.type === 'attributes') {
            console.log('The ' + mutation.attributeName + ' attribute was modified.');
            console.log({
              mutation, 
              inline: mutation.target.style[0], 
              style: mutation.target.style[mutation.target.style[0]]
            })


        }
    }
};

// Create an observer instance linked to the callback function
const observer = new MutationObserver(callback);

// Start observing the target node for configured mutations
observer.observe(targetNode, config);

This does not solve the problem

but could be used as a starting point for a custom solution to the problem.

custom diffing of each element replacing old values with the latest values you could end up with a diff of all changes up to this point using your own maintained list.

This could be a pr to each of the browsers or created as a chrome extension. Goodluck, wanted to present a possible solution instead of saying it was impossible.

Upvotes: 0

Amir Fawzy
Amir Fawzy

Reputation: 468

That depends on how you apply css fixes.

  • If you apply css code inline,you can't get a file with list of fixes you made.

  • If you made your changes in inspector-stylesheet you can find that file with all your fixes

    Go to Source tab > from the left list open localhost > you can see file called inspector-stylesheet.

    Which will show all your fixes.

    custom css fix (image)

    css changes file (image)

Another way to pick your css fixes from 'Elements' tab in dev tool you can easy copy edits you made and paste it in your css file of your project or you can edit source file itself from 'Source' tab in dev tool you have two things to do to keep what changes you made:

  1. By pressing Ctrl + S or Cmd + S to save changes and automatically will save changes in your root css file in your project files.

  2. You can copy and paste changes from dev tool to your css file in your code editor

Upvotes: 6

Related Questions