Your comments

Hi Zoltan (and Katie),


Unfortunately, I couldn't reproduce this bug (only tested on the stable Chrome channel - I don't support beta, dev nor canary because, well, they're not stable) and here's why:

The extension uses a function provided by Chrome to determine the top-most (last focused) window (chrome.windows.getLastFocused) and if some other window than the one you expected got resized, then it happened because there's a problem with Chrome itself reporting the wrong window, not the extension.

Simply put: whichever window Chrome says is the focused one, that's the one I resize.

You might want to try to make sure the window you want to resize is actually focused by clicking first somewhere inside it and only afterwards try to resize it using the extension.


I'll leave this issue open for now as I'll investigate a bit more, but I strongly doubt there's anything I could do to fix it. :(



Best Regards,


Ionuț B.

I'm sorry; this doesn't seem to be related to the Window Resizer extension, but to the Chrome Webstore or your Chrome browser. I'm afraid I can't help you with that.

Regards,
Ionuț
Hi Andrew,

Thank you very much for your detailed feedback. From what I can see in the video, it looks like the problem is only with the "mobile" presets, those that are trying to set a certain width and height for the viewport.
I'll look into it this week-end.
Meanwhile, could you please try forcing the extension to use a devicePixelRatio of 1, by going to the extension's settings and checking the "Ignore device pixel ratio" checkbox? (like so: http://screencast.com/t/jyEBUzTd)
Also, can you please try zooming the page to 50% and 200% and let me know what happens when you use the extension with zoomed in/out versions of the same page?

Best Regards,
Ionuț
I'll remove the default keyboard shortcuts with the next update (or maybe set them to something else, that wouldn't interfere with keyboard combinations that are already in use). I realize now those were some pretty poor choices, and I apologize for that!
Until then, you can disable or set them to whatever you want by going to "Chrome Menu > More tools > Extensions", scrolling to the bottom of the page and clicking on "Keyboard shortcuts" (bottom right).

Regards,

Ionut
Hi,

You can export/import data from the "Sync" page, in the extension's settings, like this:
http://screencast.com/t/fuYHnJh5P8

Regards,
Ionut
Yes, I forgot to mention that it won't work on pages you opened before installing the extension or on pages you opened before changing that setting, without refreshing them. The code needed to display that popup is loaded when the page loads so, if the tooltip is disabled, it won't load at all, even if you enable it, unless you refresh the page afterwards.

Also, it won't work on certain special pages, like Chrome's "New tab" page (or any other internal pages, like the "Downloads" page, "Settings" page, etc. It also won't work on any of the Chrome webstore pages, so it won't show if you try to resize the page while you're still on the extension's install page. This is a Chrome security feature and is true for all extensions; no extension is allowed to alter those pages.
Hi guys,

Sorry for the late reply but I was away for Christmas.

Anyway, it is definitely "retina" related, but the previous behavior was broken.
The thing is, on retina displays 4 screen pixels make 1 CSS pixel (meaning a Device Pixel Ratio of 2) so, if you want to view the page at 320 x 480 (CSS) pixels, you have to double the width and height of the viewport and resize it to 640 x 960. To test this yourself, you can open the Developer Tools console and check the values of window.innerWidth, window.innerHeight and window.devicePixelRatio.

This also happens on zoomed pages. A 800 x 600 tab zoomed at 200% on a non retina display with a default DPR of 1, will report half the dimensions (400 x 300) and a DPR of 2. The same tab (800 x 600) on a retina display will report a quarter of the size (200 x 150), but a DPR of 4.

All of the above are Chrome facts. This is how things work and it's not something my extension does.
If you don't like this (or don't agree that this is how it should work), there are two options for you:

1) There's a new setting in Window Resizer that allows you to ignore the Device Pixel Ratio completely and always behave as if it had a value of 1. This is how it previously worked, but remember that 320 screen pixels will only display 160 CSS pixels. This is useful if you don't care about the actual CSS pixels or the zoom level of a page and you just want the viewport to have the size you asked for. To completely ignore the DPR just click on the extension's icon then on "Settings"; on the "Settings" page, make sure the checkbox under "Ignore device pixel ratio" is checked. Here's a short screencast of what that does: http://screencast.com/t/WCljMoCly1

2) If CSS pixels are important to you, but it bothers you that the window becomes too large and it may not fit your screen, then you should ignore the above advice and, instead, zoom out the tab you're testing to 50% first and only after that use the extension to resize the page.
Unfortunately, it is not (yet) possible for me to automatically zoom out the page from the extension so you have to do it manually. There is an API for extension developers to be able to programmatically set the zoom level of a tab, but it's not on the stable Chrome channel yet so it is not allowed in extensions published to the Chrome Webstore. As soon as that is available, I will add a "per preset" setting so you can specify the desired DPR for each resolution you want to test.


Regards,

Ionuț