Dine kommentarer

Hello there,


That was an error message meant for you! :)

It (clearly) tells you that the browser doesn't allow you to make the window as narrow as you wanted. Besides that, you also get a hint on what you could do to get around that.


Basically, in this specific situation, you have two choices:


1. Zoom in (<CMD> + <PLUS_KEY>) to around 150% and try again. This works if what you really wanted was a narrow viewport (not window). Even though the window itself is larger, the viewport is measured in CSS (virtual) pixels, which would mean that you basically increase the size of a virtual pixel to 1.5 of a physical pixel.

A zoom of 200% means one CSS pixel equals 2 screen pixels, which is exactly what happens on retina screens.


2. Use the "Open as popup" tool, which is the second button in the right hand side column of the extension's menu (that button with an arrow on it), or just press "P" on your keyboard while the menu is visible.


I hope this helps!


Best Regards,

Ionuț

Hello Anton,


I don't speak Russian so I used Google Translate - I hope it got it right.

My guess is you're using the extension to manage your windows across the screen (many other users do the same, that's why I think you're one of them too). However, the main purpose of this extension is to help web developers test the websites they are building at certain fixed dimensions so it's important for them to get the window at just the right size, not the minimum or maximum allowed by their screen size. This is why the new version cancels an impossible resize action and warns the user that the request couldn't be completed (and gives a hint on what could be done to fix that). So, for the purpose of the extension and the majority of the users, the new behavior makes more sense.


I'm sorry, but, for now, you have only one option: edit the presets to be no larger than the size allowed by your display. I'll consider adding an option to use the old behavior, but that is definitely not going to happen when the first official stable release hits the webstore.


Best Regards,

Ionuț


P.S.: I'm also considering creating a separate extension, aimed specifically at managing your windows' size and position across the screen, but, again, that wouldn't happen in the near future (if ever).

This has been fixed and an update will be available sometime this week.

Hello Daniel,


That's an interesting idea. Just to make sure I got it right: you want the aspect ratio to be displayed in the presets list, next to the width and height, right? (I'm thinking something like this, maybe?)


Just to be clear, it's most likely that any new features won't be added to the initial release. Right now, I'm fixing bugs and figuring some other stuff out, but your idea is a good candidate for a 2.1 release.


Best Regards,

Ionuț

Hello Craig,


Thank you for reporting the bug! Someone else sent me an email this morning mentioning this so it was already on my radar, but it never hurts having confirmation from multiple sources.


Best Regards,

Ionuț

Hello William,


Thank you for reporting this! You make a good point.

There is an option to change the icon type, but I don't think that would work either, with your theme.

(settings - popup - disable "Use a monochrome icon")


Can you please tell me which theme you're using so I can test some variations of the icon and see how it would look?


Regards,

Ionuț

Hi,


The extension doesn't actually reads, writes or changes any of your data, but it needs that permission because:


  • One of the extension's features is displaying a tooltip when manually re-sizing the window. The UI for this is created by adding some HTML, CSS & JavaScript code to all the pages a user visits. In order to do that, the extension needs access to modify a page's DOM (if you're not a developer, just know that the DOM represents the internals of a page), but, if it can access everything in the DOM (the data a page contains, the forms you submit or your browsing history on that tab) it doesn't mean it actually does read it or does anything with it. It just needs to access the body of a page and append a new element to it.
  • Another reason those permissions are required is because people sometimes need to re-size the window so that the viewport is a specific size. (The viewport is the area where the page is rendered, without the borders and any other browser UI). There is no way to tell the browser to make the viewport a certain size so the extension needs to tell it to make the window the size you want the viewport to be plus the size of its borders. However, there is also no straightforward way to determine the size of the borders so the extension reads the size of the current window, then takes a screenshot of the page (it is possible to capture an screenshot of the viewport) and finally, it subtracts the size of the generated image from the size of the window and that represents the borders' size. It then adds that size to the desired size of the viewport and tells the browser to re-size the window at the resulting width & height. :) It's pretty convoluted, but until recently it was the only way to reliably read the viewport's size. So, what's that got to do with your browser's history? Well, the (internal) permission an extension has to request to be able to take a screenshot of a page is the same as before: it needs to be able to access everything related to the current tab / page and, even though it reads none of that personal info and it destroys the screenshot right after it was taken and measured, those permissions come as a package.


I hope my answer makes it clear why you see that message.


Best Regards,

Ionut


P.S.: I hope you don't mind I change the visibility of this ticket to public, so others that might be wondering the same thing can see my answer.

You can just disable the tooltip while you're using that toolbar, if it bothers you that much...

Anyway, this is fixed in v.2 and won't be an issue anymore pretty soon.

Hi John,


1. The ability to alter only one side of the window (the width in your case) has been added a long time ago. Edit the presets you're using and delete their height value. This way, you'll set the width to whatever you want and the height of the window will remain unchanged.


2. That is not possible because extensions developers have no means to modify the size or position of the Developer Tools.


Regards,

Ionut

Sorry, but that's not possible. Negative offsets represent coordinates on multiple monitor setups and I can't change that.


Let's imagine that you have 3 Full-HD monitors (1920 x 1080) and the middle one is the primary monitor. That means the top left corner of that monitor has the coordinates [X: 0, Y: 0]. In that case, if you specify a coordinate of [X: 2000, Y: 300], that means the window will be placed at 80 x 300 on the 3rd monitor while, if you'd use [X: -1000, Y: 300], that would place the window at 920 x 300 on the 1st monitor.


I hope that makes sense; I didn't came up with it, it's just the way computers work. :)




Leveres av UserEcho