I am getting a "Mobile version not available" modal that wont go away on its own on desktop. I can trick it by making my browser full screen, refreshing, then resizing it back to a half sized window.
This should be fixed now.
Show HN: Test your website on 180+ device viewports (with multi-device mode)
11–20 of 53 posts
Re: Show HN: Test your website on 180+ device viewports (with multi-device mode)
#12I am getting a "Mobile version not available" modal that wont go away on its own on desktop. I can trick it by making my browser full screen, refreshing, then resizing it back to a half sized window.
This should be fixed now.
Nice, that seems to be fixed now. Thanks!
I noticed another possible bug. When trying it out on your website, it reports an "Invalid URL" error.
Re: Show HN: Test your website on 180+ device viewports (with multi-device mode)
#13Re: Show HN: Test your website on 180+ device viewports (with multi-device mode)
#14Earlier quoted context omitted.
Nice, that seems to be fixed now. Thanks! I noticed another possible bug. When trying it out on your website, it reports an "Invalid URL" error.
Can you share the URL you're testing?
Yep!
The detailed text on the modal says: We can only load URLs that pass standard pattern checks.
Re: Show HN: Test your website on 180+ device viewports (with multi-device mode)
#15Earlier quoted context omitted.
Can you share the URL you're testing?
Yep! https://viewport-tester.com The detailed text on the modal says: We can only load URLs that pass standard pattern checks.
Haha funny! Yeh we disabled that, in part, because it can result in an infinite loop.
Re: Show HN: Test your website on 180+ device viewports (with multi-device mode)
#16Earlier quoted context omitted.
Yep! https://viewport-tester.com The detailed text on the modal says: We can only load URLs that pass standard pattern checks.
Haha funny! Yeh we disabled that, in part, because it can result in an infinite loop.
Hahahahahaha, ahhh that makes sense. I didn't think about it getting suck in a loop.
Re: Show HN: Test your website on 180+ device viewports (with multi-device mode)
#17Targeting specific viewports is such a wrong way to go about it. Just resize your browser (or use the built in responsive design preview and freely resize that) to see if you reflow in a sane way. A single drag gets you hundreds if not thousands of different widths and aspect ratios tested.
Re: Show HN: Test your website on 180+ device viewports (with multi-device mode)
#18I am getting a "Mobile version not available" modal that wont go away on its own on desktop. I can trick it by making my browser full screen, refreshing, then resizing it back to a half sized window.
This should be fixed now.
Mobile Safari set to "always show desktop version" still triggers this modal.
Edit: even if you click "Request mobile version", the modal is there
Re: Show HN: Test your website on 180+ device viewports (with multi-device mode)
#19Targeting specific viewports is such a wrong way to go about it. Just resize your browser (or use the built in responsive design preview and freely resize that) to see if you reflow in a sane way. A single drag gets you hundreds if not thousands of different widths and aspect ratios tested.
Thanks for the comment @account42 Agreed that a really-great responsive site is one where specific viewport dimensions don't matter. One thing we've run into (and want to test for) is users mentioning they're using a specific device and having issues.
In those cases, it's helpful for us to really quickly choose from a list the device, and view the site. That way, we don't need to know the exact dimensions of the device, and can also test a possible fix for that device against other viewports.
Re: Show HN: Test your website on 180+ device viewports (with multi-device mode)
#20Earlier quoted context omitted.
This should be fixed now.
Mobile Safari set to "always show desktop version" still triggers this modal. Edit: even if you click "Request mobile version", the modal is there
Unfortunately we don't have support for mobile Safari yet. It has to do with some performance challenges related to drawing multiple iframes to the page. Hope to get that fixed soon.