Support & Troubleshooting

Have an issue, bug report, or feature request? We're here to help make responsive testing seamless.

contact@sinansarikaya.dev · security@sinansarikaya.dev

🐛

Bug Reports

Found unexpected behavior or a website framing issue? Open an issue with steps to reproduce on our official GitHub tracker.

Open Bug on GitHub ↗
💡

Feature Requests

Have ideas for custom device profiles, new compare modes, or developer workflow enhancements? Let us know in discussions.

Submit Feature Request ↗
📖

Technical Docs

Explore detailed guides on manual installation, keyboard shortcuts, header relaxation troubleshooting, and synchronization.

Read Documentation →

Common Troubleshooting Tips

1. Why is an iframe showing "Refused to connect" or a blank screen?

Certain high-security websites (e.g. banking portals or Google login pages) explicitly prohibit framing or require full cookie authentication. While ViewGrid automatically strips X-Frame-Options and CSP: frame-ancestors for sub_frames, sites requiring top-level navigation must be tested in a dedicated window.

2. How do I test local development servers like Vite, Next.js, or Webpack?

Simply type your local URL (e.g. http://localhost:5173 or http://127.0.0.1:3000) into ViewGrid's top address bar. Because ViewGrid runs locally as a native browser extension, it has direct access to your local loopback interfaces with zero proxy lag.

3. How do I temporarily test without device frames?

Click the ▣ Frames button in the workspace toolbar or press F on your keyboard to toggle between authentic hardware bezels and clean borderless cards for maximum screen density.

4. Need direct assistance?

You can reach the author directly at sinansarikaya.dev or via the ViewGrid GitHub repository.