How is this different from the built in DevTools support?

I'll also soon be adding the ability to view content across multiple devices directly in a single tab; many users have been asking for this feature. For now, I'm just working on compatibility issues with different operating systems and other related matters. I haven't gotten around to it yet, but it's already in development.

▲

mongrus 8 hours ago | parent | prev [-]

Display. The desktop is displayed in a convenient (unadjusted) format, plus phone frames allow you to beautifully present the site to clients, employers, and others. Everything is in one minimalist panel. The goal was to avoid overloading the extention like competitors and to make everything work in one tab, again, without cropped visuals)

▲

beardyw 6 hours ago | parent [-]

Even DevTools doesn't pop up a keyboard when you type. That has a significant effect on the page and fails to present a realistic expectation.

▲

mongrus 5 hours ago | parent [-]

I agree—no tool, including DevTools, simulates the on-screen keyboard and its impact on the viewport. Mobile View is still a tool—for a quick preview of the responsive design and presentation (to a client/employer), not a full emulator for final testing.

For a truly accurate test (keyboard, touch, performance), you still need a real phone—this is stated on the website and in the Chrome Web Store description. But as an idea for future implementation, it's excellent! Thanks for the feedback; you actually dug into it and thought about what was missing)

▲

beardyw 4 hours ago | parent [-]

> dug into it and thought about what was missing

Got bitten by it. A fixed input at the top of the screen just disappeared. Needed an entry in the page meta to sort it.

	▲	mongrus 26 minutes ago \| parent [-]
		That's a good, concrete example. This is the blind spot of preview tools. These are the kinds of bugs — viewport behavior with keyboard input, 100vh glitches — that the preview won't show at all because there's no keyboard. Now if i go for keyboard/viewport simulation, I'll know where to start looking and what will help me fix them (interactive-widget=resizes-content, etc.).