> No unuseful, duplicated, overridden, or longhand CSS
How does this differ from doing Cmd-Shift-C, selecting an element, and checking the Computed tab in Dev Tools?
How does this differ from doing Cmd-Shift-C, selecting an element, and checking the Computed tab in Dev Tools?
* How is this better than "Computed Styles"? > When you copy CSS from “Computed Styles”, aside from the declarations being longhand and bloated, it transforms all measurement units such as %, em, rem in pixels (px). This could break your website on mobile devices.
"Computed Styles" also don’t give you pseudo-classes, pseudo-elements, media queries, and keyframes styles, and don't copy multiple elements at once. CSS Scan does, and it gives you the original units and everything you need effortlessly.
This is known as the "computed value" https://www.w3.org/TR/css-cascade-4/#computed. The Computed tab will still display the specified values in the units they were declared in if you expand the list of matching selectors.
> also don’t give you pseudo-classes, pseudo-elements
True! A useful feature you've added; but if I select a pseudo-element in my inspector I can still see (and copy) the computed value
> media queries, and keyframes styles
This is also provided by just clicking the arrow next to a selector and expanding the matching ruleset in the Computed tab. Your product reduces the effort a great deal though! Love the demo.