Responsive Viewer

@kunalbodke Do you really can't afford $7 or you just don't wanna pay for other people products?

@brunolemos that's a little harsh. Sizzy's cheapest plan, for instance, is $7 per month or $60 a year. Nothing wrong with using an open source replacement if it does what you need it to do.

@brunolemos I meant to say I cannot justify paying for Sizzy. But I see how you look at people. So, my rational is since I am not reviewing coded designs every week or month. Our release cycles are quarterly.

@kunalbodke “I cannot justify based on my low usage” is a more honest take than “I can’t afford”. 👍

@brunolemos yeah, typed too fast, without thinking a lot about it. ;) I was just excited this thing is out there!

@kwsim thanks for your review glad that you loved it, I will fix the other the reported bugs and let you know from this page.

@emiledpretorius Thanks, I pushed a new version of the extension and it's under review , must be available in few days.

@solaimankmail awesome, I'll look out for the update.

@francoolaami Hi, I built this project few months ago, I'm planning to refactor the code little bit to support firefox soon.

@solaimankmail please do, many of us (and even more in tech scene) are separating form chrome/chromium.

@francoolaami https://addons.mozilla.org/en-US...

@solaimankmail why do you need so much persmissions ? http://imgur.com/hRuwruL

@francoolaami these permissions required to make it able to show any website inside the iframe. first permission: is to modify websites header inside the iframe to remove x-options header. 2: some websites refused to open after first visit from the action and it fixed by clearing the service works. 3. I think it's a basic permission. 4. this is required to access tabs api to create new tab of the extension. 5. it is required to detect when navigation occurs to and to carry the user agent to next page. hope this clarify. also you can checkout the source code on github https://github.com/skmail/respon...

@herbosa Thanks, there's no difference in the rendering side, the main difference is the ability to show multiple screens in one view, there are more features I'm working on and will be released soon.

@vsotiris That's right, the extension depends on the user-agent to display the page since it's impossible to emulate other browser rendering engines without using third-parties or actual devices.