Skip to content
This repository has been archived by the owner on Apr 26, 2024. It is now read-only.

Causes issue with Chrome Inspector #6096

Open
tim92109 opened this issue Jun 8, 2015 · 5 comments
Open

Causes issue with Chrome Inspector #6096

tim92109 opened this issue Jun 8, 2015 · 5 comments

Comments

@tim92109
Copy link

tim92109 commented Jun 8, 2015

When using prefixfree, when you inspect an element with Chrome Inspector, you will no longer see exactly which line number of your style sheet that the class or ID is being called from. Real pain to have to search your style sheet every time you want to edit an element.

@nlourenco
Copy link

Same issue happened with me and its not limited to Chrome. All external styles are moved inline.

@tim92109
Copy link
Author

Yea... I loved it at first, but stopped using it as it ended up eating more time than saving time.... just from having to search for elements.

@LeaVerou
Copy link
Owner

LeaVerou commented Jan 5, 2016

Unfortunately, that's unavoidable at the moment with any JS solution that modifies CSS, as it has to re-request the stylesheet.
Perhaps sourcemaps could help, though I haven't seen any such use of them.

@tim92109
Copy link
Author

tim92109 commented Jan 5, 2016

Makes sense. BTW, if you're only coding for modern browsers, is there still a use for prefixfree in 2016?

@LeaVerou
Copy link
Owner

LeaVerou commented Jan 6, 2016

Certainly not as much as in 2012 when I made it. I still use it, but rarely.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants