I am not entirely sure, as a web developer I've never seen a certificate pass all SSL checkers yet chrome and firefox on my computer (up-to-date) won't load them. I pondered a MITM attack but it's literally the only site this happens on - not exactly sure what is causing the https to not load on my end.
edit All I get is "ERR_SSL_PROTOCOL_ERROR" - I'm pretty sure I tested this link out at work but I will again on Monday to verify it happens there (currently I'm tethered as well as vpn'd to PIA and I don't think my provider T-Mobile is doing anything to block this one ssl)
We're working on it! We heard this feedback a few times. Our intention is to make mobile the default in DevTools, but we don't want to make the experience worse for people building Desktop sites. So we'll come up with a better solution. Stay tuned!
Author of the linked post here. Definitely wasn't our intention to leave Desktop behind. A mobile-only world isn't better than a Desktop-only world. Thus, mobile first. Start with the most common scenario and build your way up to other platforms.
That being said, I realize that some apps and intranet sites will be Desktop only by design, and that's fine. We don't want to make your experience worse. Any feedback on that front is greatly appreciated.
Is it the most common scenario in development? Seems to me you've got it backwards. You've confused consumers of websites with numbers of developers.
For example I see far more job adverts for internal tools developers, which are going to be by and large desktop only, than mobile-first website developers.
So I'd have thought the number of desktop only web app developers vastly outnumber the number of mobile-first web developers. I think you're wrong with the word 'some'. Most is the word you should be looking for.
Don't forget you're emulating a phone without touch. It's useful, but it's only part of a mobile testing process. So you're making what is a fairly broken process the 'focus', which seems pretty odd.
Mobile is also feature poor compared to desktop so generally needs less testing. It's the less intense part of any site because of the form factor. That's why you're not playing Fallout 4 on your mobile, you've got a little companion app for it instead.
Finally, for most mobile websites there will be a desktop only admin section. And it's desktop only because it has huge tables, with lots of sortable columns. On multiple pages. Common admin interfaces found in any website or app. So while a desktop site can often exist without a mobile component, it's rare for a website to exist without a desktop component.
Speaking of mobile development, something that's been annoying me for a long time is that while you can "emulate" the devicePixelRatio of a mobile device, it doesn't actually seem to do anything meaningful.
For example, my phone has a resolution of 1080x1920 and a dPR of 3, so the viewport size is 360x640.
If I set these properties in Chrome Dev Tools, I just get a 360x640 rendering out of it. I'd like to be able to get a proper 1080x1920 rendition of the device screen too! It doesn't matter that it will look absolutely enormous on my desktop screen, I just want to make sure that my code and styling actually works like I want on it. I really shouldn't need to use an actual device for something as simple as this.
OP here. Thanks for the bug report! I'll fix. It's true, haven't used IE in the while, but that wasn't the point of the article. I care deeply about the web as a whole, and all of its evolution.
OP here. I actually agree, and that seems to be Google#s stance right now, from what I've heard (I work for Google but wasn't involved in the technical work on this feature so far). We might need an API that is slightly more low level but achieves the same. My point was that we need this functionality, and no other API offers it, so I took anything I could get :)
It's by design that our site is only available via HTTPS. Is there a good reason for why you can't consume the HTTPS version?