Revisiting Firefox’s DevTools makes a solid case for FF.These Dev Tools are full-fledged suites nowadays, feature discovery and developing the corresponding “muscle memory” to use said features become a real challenge.
It’s a shame because otherwise, it’s clear that the Firefox and Chrome Dev Tools are learning from each other, with some of the cutting-edge functionality shared by both.īoth now do natively what used to require a bunch of separate extensions, from playing with the viewport to test responsive designs, to color picking/eyedropping and more. However, in the pursuit of our ideal workflow, I tried CSS-X-Fire with it, and unfortunately it’s not supported. Like many people I gradually moved to Chrome over the years, after suffering from memory leaks in Firefox and see that browser lose its edge. So I’ve installed Firefox Developer Edition, which comes with Firebug.next. In search for the perfect modern toolset, I revisited Firefox as a browser for development. More seriously, I’m trying to remove all these grains of sand that add up and in get in the way of establishing and maintaining flow/zone. Since I’m willing to work hard to get tools that will let me be lazy later, I kept looking for a better way. This is great in its own right, though the process to find then edit CSS selectors in Firebug is not very streamlined, because you have to go back and forth between Inspect (which opens the HTML tab) and CSS (where you have to search for your class). …BrowserSync injects the compiled style.css in the browserĪfter some tinkering with CSS-X-Fire, I’ve found it works best with “Currently opened files” checked, which means you need your source LESS/SCSS to be opened in PhpStorm.
0 kommentar(er)
