Norman window and incognito window issue
When user have a normal and incognito window open in the same time and user tries resize the normal window but 'Window Resizer' will resize the incognito window instead.
Svar
This also occurs with more than one normal window open. Resizer will only work on the "newest" window.
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.
Thanks for the quick reply -
Based on the function you're using, I think you're right that it's an issue with Chrome itself. I've been using your plugin for over a year (I love it, by the way!) and this is the first time I've experienced the problem. However, I did notice Chrome updated in the background sometime between yesterday evening and this morning.
Per your suggestion, I exhausted all testing options and found when the secondary window was minimized, Chrome would bring the minimized screen into focus and resize it - although not resized to the dimensions I selected. Hopefully their development team will notice an error with their latest update and quickly work to resolve it..
Hello my friends,
I have found a workaround for this and I just published an update to the Chrome webstore.
It should be live in an hour or less.
Best Regards,
Ionuț
P.S.: For anyone interested, the workaround was to use
chrome.tabs.query({lastFocusedWindow: true}) (the tabs are populated with the correct window ID) instead of chrome.windows.getLastFocused()
P.S.2: I have created issue 546696 on the Chromium issue tracker, in case you're interested about the updates on this Chrome bug.
Kundesupport af UserEcho
Hello my friends,
I have found a workaround for this and I just published an update to the Chrome webstore.
It should be live in an hour or less.
Best Regards,
Ionuț
P.S.: For anyone interested, the workaround was to use
chrome.tabs.query({lastFocusedWindow: true})(the tabs are populated with the correct window ID) instead ofchrome.windows.getLastFocused()P.S.2: I have created issue 546696 on the Chromium issue tracker, in case you're interested about the updates on this Chrome bug.