You make a good point!

Sorry, there's no way to disable it at the moment. I'll add a way to disable it in the next couple of days.

Best Regards,

Ionuț

P.S.: This version has been tested by ~30.000 users during the last 6 months, but no one was in this situation and it didn't occur to me something like this might happen. Again, I apologize for the inconvenience.

Hi Jonathan,

Here's another principle: display reliable information or don't display it at all.

Using the API currently provided by Chrome, it is not possible to implement this in a reliable way, that's why I chose not to do it at all. In the 7 years this extension has been available in the store and out of the ~600.000 users it has, you are not the first one to suggest this feature and, like many times before, I can only promise that I will look into it again, see if anything's changed and if there's any way to hack it.

Best Regards,

Ionuț

P.S.: Just as an example of the intricacies this feature presents, imagine the following:

- You have a Window(1) with 3 tabs

- Tab(2) has the developer tools opened

- While Tab(1) is focused, you apply a Preset(A) which sets the viewport to 1280x720 and you store that information Tab(1) = Preset(A)

- Now you switch to Tab(3). What should happen when you open the popup? Should any preset be selected? Tab(3) should be exactly the same as Tab(1), so it makes sense to display the same preset as selected. That means maybe we should maybe store the selected preset at the window level so forget that Tab(1) = Preset(A) and just remember that Win(1) = Preset(A)

- But now you switch to Tab(2), which, remember, had the developer tools open. That means the viewport of Tab(2), although in the same window as Tab(1), is smaller than the selected preset. This means that we can't display Preset(A) as selected while on Tab(2). This means that we can't rely on storing the selected preset at the window level.

- How about we don't store it at all and just see what the window/tab size is for the currently focused window when the popup opens? Ok, let's try that!

---

- We set the height of the viewport on Tab(1) to 600, using Preset(D). Let's assume that this makes the viewport 600px tall and the window 640px tall.

- We have another Preset(C) (that's before D) that targets the window and makes it 640px tall

- If we click on Preset(D), which preset should appear as selected the next time the presets list is opened? Since we previously decided that we won't tie a preset to a window or a tab, we must rely on measurements, but the measurement matches 2 different presets and the one we clicked on is the second in the list. So, even though we'd click on Preset(D), the measurement would say that Preset(C) is active.

Like I said, I can't find a reliable way to display the preset that matches the current window/tab combination!

I'm sorry, but is it really that hard to tell if the orientation is landscape or portrait just by looking at the window? :(

Hi Vladislav,

You can achieve the same thing as before by using a keyboard shortcut:

1. Open the "Settings" dialog

2. Go to "hotkeys"

3. Click on "configure the shortcuts"

4. Find "Window Resizer" in the list

5. Set a shortcut for "Cycle presets"

"Cycle presets" does the exact same thing as in the previous version.

As for your original request, it won't be implemented as it's beyond the scope of this extension, which is not managing windows, but helping web developers do their job.

Best Regards,

Ionuț

It was there before and it still is, working as intended. :) The problem was that you didn't use it in the previous version, but didn't notice it because it only appeared when resizing the window while the new version also displayed it when loading a new page.

The new behavior has been removed and the tooltip will only be displayed when resizing the window (if not disabled from the settings).

Regards,

Ionuț

The same reason as in the question posted by the guy before you, the one you didn't read before posting this one! :)

Anyway, I published an update that should fix this. (v2.2.1 - 2017.08.31)

Hi Charlie,

If the presets are the same as before the update, then they are broken and you should update them with the correct values. The old version of the extension tried to resize the window to the desired dimensions but if it couldn't it would fail silently and leave the window as close as it could to the desired sizes. Unfortunately, that behavior is not desirable for the intended audience of this extension (web developers) and it has been removed, with the extension reverting the window size if it couldn't set it to the desired dimensions (usually due to Chrome restrictions).

If you want to achieve the same thing, you need to simply edit the presets and set correct width and/or height values for the window size and not bogus ones like 100 x 100. If your screen's resolution is, let's say, 1920 x 1080, rotated to 90 degrees it would be 1080 x 1920 so your preset should be width=1080, height=960, left = 0, top=960.

Regards,

Ionuț

Hi,

Open the "Settings" page then, on the top row, you'll see 3 items: "popup", "tooltip" & "other". Click on "tooltip" and make sure the toggle for automatically showing the tooltip is off.

I'm sorry for the trouble this has caused; normally, it should have respected your previous settings... I'll look into it!

Best Regards,

Ionut

Hi Jim,

You tried to "rotate" the viewport to a height of 1024px while your screen only had 900px, which resulted in the error you mention. This is because the OS doesn't allow a window to be taller than the maximum screen height.

I know the error message is not clear enough and I'll try to find better wording for it, but, as suggested in that message, the solution in your situation is to zoom out the page to something like 75%, resize the viewport again to 1024x768 an then use the rotate tool again.

Zooming out is equivalent to changing the DPR (devicePixelRatio), which means that for a 75% zoom you get a 0.75 DPR (or 1.5, if your Mac has a retina display), resulting in a greater amount of CSS pixels displayed on the same amount of physical pixels. More exactly, for a 75% zoom you'll get 1024 CSS pixels rendered as 768px on your screen.

I hope this makes sense!

Best Regards,

Ionut

That's weird... No, it's not supposed to use that much memory! I have 3 Chrome windows with 68 opened tabs and it was using 4 MB when idle. When I started resizing the window, it went up to 24-30 MB but started to go down as soon as I stopped playing with it. I'll try playing with it more to see if I can get it to go closer to what you're experiencing.

Thanks for reporting this!