Your comments
Yeah, it's on hold... It's not as easy as it seems.
The thing is I can't just measure the scrollbar width/height (which is different based on OS and user settings) and just add it to the window size, because a page might have a vertical scrollbar at 640px height but it might not have at 720px. Also, a page might trigger the scrollbar on user interaction: just think about an accordion menu which is expanded on click and increases the body's height, triggering the scrollbars, which will narrow the viewport...
Anyway, I decided the best way to handle it would be to completely hide all the scrollbars on resize (using ::-webkit-scrollbar) and dynamically add some custom scrollbars using JavaScript and handle scroll events myself. This would give it more of a mobile look and feel, but there are still some gotchas.
For example, what should happen after you resize the window and navigate to some other page of the site you're testing? The script injected by the extension is lost and the default scrollbars will be visible. Should the extension remember that this tab had custom scrollbars and auto-enable them on page load? If so, what if the user wants the default back? Should there be a button in the extension's drop-down menu to toggle the custom scrollbars?
So, you see, there are lots of questions to be answered and I didn't have the time... (After all, this is just a pet project that doesn't put food on my table :D )
Still, I started working on a new version and I already have a functional prototype of the custom scrollbars I mentioned above, but I can't say when a beta version will be ready for the public...
The thing is I can't just measure the scrollbar width/height (which is different based on OS and user settings) and just add it to the window size, because a page might have a vertical scrollbar at 640px height but it might not have at 720px. Also, a page might trigger the scrollbar on user interaction: just think about an accordion menu which is expanded on click and increases the body's height, triggering the scrollbars, which will narrow the viewport...
Anyway, I decided the best way to handle it would be to completely hide all the scrollbars on resize (using ::-webkit-scrollbar) and dynamically add some custom scrollbars using JavaScript and handle scroll events myself. This would give it more of a mobile look and feel, but there are still some gotchas.
For example, what should happen after you resize the window and navigate to some other page of the site you're testing? The script injected by the extension is lost and the default scrollbars will be visible. Should the extension remember that this tab had custom scrollbars and auto-enable them on page load? If so, what if the user wants the default back? Should there be a button in the extension's drop-down menu to toggle the custom scrollbars?
So, you see, there are lots of questions to be answered and I didn't have the time... (After all, this is just a pet project that doesn't put food on my table :D )
Still, I started working on a new version and I already have a functional prototype of the custom scrollbars I mentioned above, but I can't say when a beta version will be ready for the public...
Hi Tom,
I just pushed an update (should be available within the next hour) which adds a new keyboard command that toggles the bottom right hand tooltip without re-sizing the window; you just press whatever keyboard combination you chose and the tooltip appears (press again to hide). There are a few things to note though:
* As usual, the tooltip doesn't work on the Chrome Webstore pages, on any of Chrome's special pages (settings, downloads, extensions, etc) or on files loaded using the file:/// protocol or incognito pages if you haven't explicitly enabled the extension to work in those last two situations on chrome://extensions/?id=kkelicaakdanhinjdeammmilcgefonfh
* The tooltip needs to be enabled. If you disabled it on the extension's "Settings" page under "Tooltip visibility", it won't work
* There's no default keyboard shortcut so you need to add your own. If you don't know how to do that, here's an article explaining the steps.
Regards,
Ionuț
I just pushed an update (should be available within the next hour) which adds a new keyboard command that toggles the bottom right hand tooltip without re-sizing the window; you just press whatever keyboard combination you chose and the tooltip appears (press again to hide). There are a few things to note though:
* As usual, the tooltip doesn't work on the Chrome Webstore pages, on any of Chrome's special pages (settings, downloads, extensions, etc) or on files loaded using the file:/// protocol or incognito pages if you haven't explicitly enabled the extension to work in those last two situations on chrome://extensions/?id=kkelicaakdanhinjdeammmilcgefonfh
* The tooltip needs to be enabled. If you disabled it on the extension's "Settings" page under "Tooltip visibility", it won't work
* There's no default keyboard shortcut so you need to add your own. If you don't know how to do that, here's an article explaining the steps.
Regards,
Ionuț
This has been fixed and the update should be available within the next hour.
Hi Jacob,
Sorry for the delay, but I guess it's better late than never, right? :D
I just pushed an update (should be available within the next 60 minutes) which adds - among other things - a new command to cycle presets in reverse order. The only thing to note is that there's no default shortcut assigned so you'll need to add your own.
I hope you know how to do that, but just in case, here's an article showing the steps.
Regards,
Ionuț
Sorry for the delay, but I guess it's better late than never, right? :D
I just pushed an update (should be available within the next 60 minutes) which adds - among other things - a new command to cycle presets in reverse order. The only thing to note is that there's no default shortcut assigned so you'll need to add your own.
I hope you know how to do that, but just in case, here's an article showing the steps.
Regards,
Ionuț
Hi Angelica,
I don't see why reverting to the exact same size is so important for you (especially since it's just some random size that you don't even know)... Anyway, it is not possible to "Undo" a re-size operation, but you can add the current size to the presets, without knowing the exact window dimension.
Here's how: http://screencast.com/t/4LazTmmSEp
In the "Add new resolution" form, you simply select the "Use current window size" option and the current size is automatically detected and update if you manually re-size the window while that option is selected.
You also have the option to use the "Use current viewport size".
* The window refers to the size of the entire window, including it's border, toolbars, etc.
* The viewport refers only to the area where the page is rendered, without the window borders, toolbars, etc. E.g. If you set a size of 1024 x 768 and the "Resize target" is set as "Viewport", then the final window size will be something like 1040 x 857. (See example: http://screencast.com/t/eA05lTXTAWf )
Regards,
Ionuț
I don't see why reverting to the exact same size is so important for you (especially since it's just some random size that you don't even know)... Anyway, it is not possible to "Undo" a re-size operation, but you can add the current size to the presets, without knowing the exact window dimension.
Here's how: http://screencast.com/t/4LazTmmSEp
In the "Add new resolution" form, you simply select the "Use current window size" option and the current size is automatically detected and update if you manually re-size the window while that option is selected.
You also have the option to use the "Use current viewport size".
* The window refers to the size of the entire window, including it's border, toolbars, etc.
* The viewport refers only to the area where the page is rendered, without the window borders, toolbars, etc. E.g. If you set a size of 1024 x 768 and the "Resize target" is set as "Viewport", then the final window size will be something like 1040 x 857. (See example: http://screencast.com/t/eA05lTXTAWf )
Regards,
Ionuț
Hi,
Nope, this is new to me, but I discovered what the problem is and I'll be fixing it today.
Regards,
Ionuț
Nope, this is new to me, but I discovered what the problem is and I'll be fixing it today.
Regards,
Ionuț
Hi Jacob,
I'll add this on Monday. :)
Regards,
Ionuț
I'll add this on Monday. :)
Regards,
Ionuț
Hi Errol,
I'm not sure what the problem might be and I don't have the time to look into it until Monday. In the meantime, could you try to add your own presets but set them at half the desired size and see if that works? E.g: use 512 instead of 1024.
I'm willing to have a chat with you over Skype or Google Hangouts on Monday, just let me know which one do you prefer and the time when you're available (hour and timezone).
Best Regards,
Ionuț
I'm not sure what the problem might be and I don't have the time to look into it until Monday. In the meantime, could you try to add your own presets but set them at half the desired size and see if that works? E.g: use 512 instead of 1024.
I'm willing to have a chat with you over Skype or Google Hangouts on Monday, just let me know which one do you prefer and the time when you're available (hour and timezone).
Best Regards,
Ionuț
Customer support service by UserEcho
Sorry for the late reply, but I was away for Christmas.
Anyway, here's what you need to do (in case you haven't figured it out yet):
chrome://extensionsRegards,
Ionuț