However Firefox has been, and always will be my daily driver for all Web browsing. It's eco system is richer, noscript and the fact that it's not a Google product is a huge selling point.
However Firefox has been, and always will be my daily driver for all Web browsing. It's eco system is richer, noscript and the fact that it's not a Google product is a huge selling point.
* selecting CSS colors in other colorspace (eg. RGBA) as oppose to just hex
* throttling the network in desktop mode. I think the option just shows up in responsive design mode.
Although I dont think Chrome is "vastly" superior at this point as FF has certainly narrowed the gap.
> I've tried the Firefox inspect menu and I'm just immediately turned off and confused..
I remember feeling the same when I switched from Firebug to Chrome. It takes a few days to get used to a new UI.
I'm not sure if this is what you mean, but you can go into the dev tools config and change the default color unit under Inspector. The eyedropper will show values using the selected unit and style rules will be converted to that unit.
Im on FF Quantum 57.0 (non dev, vanilla FF) and here are my observations:
> When an XHR response comes back as HTML, there is no "Preview" tab like in Chrome.
This is consolidated in the Response tab. You can view it as raw response, or JSON (with filtering options).
> Also, the responsive testing tool doesn't have the device frames (ie, iPhone, iPad, etc)
It does now! You can select and edit a list of device.
> and it also doesn't have the little touch circle cursor that let's you drag and swipe while testing.
They do have a touch simulation mode (pointing hand icon), but it doesnt appear to work at the moment. I cant drag the screen.
> This is consolidated in the Response tab. You can view it as raw response, or JSON (with filtering options).
Yeah, I can see the raw HTML or JSON response. But Chrome actually allows you to see the rendered HTML response in the "Preview" tab. Are you saying there is a way to see the rendered HTML from the XHR response? I'm not seeing it. To see the rendered HTML, I have to copy it, create an html file, paste the HTML, then open it in a browser. That's a lot of extra steps when debugging something.
If you grab Nightly (I've been using it for a year now for frontend development and my normal browsing and it's just fine) you can test it.
Today is the first day I spent my entire day in Firefox and didn’t get angry. I love it! Ditched chrome for default browser now.
They are very open to feedback!