New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Dropdown menu does not fit in window, requires horizontal scrolling #17
Comments
Yikes, will fix and push out an update asap. Thanks! |
I've just pushed v1.0.7.5. Please let me know if this issue is fixed after updating :) |
Thanks for the quick attention, but unfortunately it is still showing the same symptoms. |
Do you remember which version it was displaying properly in? Also did you try restarting Chrome? |
I have tried restarting Chrome. It has been a problem for quite a few days, but not weeks but I did not think to check the version when it first started happening. |
Thanks, I'm working on making some minor CSS tweaks and will push an update in a couple hours or tomorrow. Side-note: something strange I noticed is that the footer in the panel in your screenshot is that of v1.0.7.3 (with the "Quick Start | Overview" links that I changed to "Documentation" in v1.0.7.4) |
New update v1.0.7.7 pushed out. Please try and close this issue if it's working for you :) |
Sorry, but it still is happening! |
Please try v1.0.7.8 and close this issue if resolved, thanks! |
(sorry for the delay in getting v1.0.7.8 to you; it's been "Pending Review" in the Chrome Web Store since I pushed it out 8:45pm eastern yesterday) |
I've been refreshing the Developer Dashboard all day to check on the status and I'm happy to announce v1.0.7.8 has been published on the Chrome Web Store within the past half hour. |
It is better - I can see more of the dropdown menu but still not all. I still have to scroll to the right to get to the X to close the window (although I usually just click outside the menu).. |
Good to hear there's some improvement, can you please post a screenshot so I can gauge the values? Thanks! |
Windows is set at medium, 125%. I have Chrome set zoomed as well, but it looks like that might vary by tab. A new default tab comes in at 125% |
@JeffryErickson has this improved for you in any way with the latest updates? |
No, sorry! (I am on .7.10 now) |
I have the same problem...is there any solution by now? |
I still have the problem, too. |
I am on version 1.0.8.5. I tried updating but Chrome is not pulling in v1.09. My system font is also at 125%. I believe my ScriptSafe options are all at their defaults. I like the one-column layout! |
@JeffryErickson please let me know when v1.0.9.0 is propagated to your machine :) I'm hoping that the one-column layout resolves the horizontal spanning issue! |
Thanks; I think I have an idea of how to resolve this, I'll look into it today and I'll keep you updated! |
I've worked on converting the font sizes and widths to be fluid and created a test build for you to try on your machines. Could you both do me a favour and test it out? https://dl.dropboxusercontent.com/u/784305/scriptsafe_test.zip Thank you! Instructions on how to install it:
Then please open a site and open the ScriptSafe panel and let me know if there is any improvement. Once done testing, you can simply remove the test ScriptSafe build and re-enable the Chrome Web Store version. |
Yes! That is working perfectly. Everything fits in the dropdown window. thank you :) |
That's great to hear! :) Allow all blocked for Session = appears when items have been blocked on a tab. Try going to www.cnn.com and click on "Temporary" to allow external resources to load, then open the panel again and this should appear. Revoke page temp permissions and revoke all temp = if you temporarily allow something in a tab, these two buttons will appear. If you're on a tab with nothing temporarily allowed, but you have temporarily allowed something in a different tab, only "Revoke All Temp" will appear. |
ahhh nice, never noticed that before, because i would've had to scoll down^^ looking forward to the next version....and thanks again for the really fast support |
Your test build worked perfectly - great! |
v1.0.9.1 Beta is now available for testing: #166 |
I loaded the Beta and everything seems to work perfectly so far. I can see the entire drop-down window. Great! |
v1.0.9.1 has been published in the Chrome and Opera stores which addresses this issue. Thanks again for your report and testing! |
@JeffryErickson very interesting! Thank you for retesting. I will re-open this issue. I just compared the changes between v1.0.9.1 beta and the stable version: v1.0.9.1_beta...master The only change I made was removing 5 pixels from the top of the panel, bringing the tab domain box closer to the ScriptSafe heading. Could you try downloading v1.0.9.1 from https://github.com/andryou/scriptsafe/releases/tag/v1.0.9.1 and loading it into Chrome following the same instructions I provided earlier in this ticket, and let me know if the panel still has the issue? (#17 (comment)) If it displays properly, then it sounds like there is a weird bug in Chrome with local extensions vs extensions added from the Web Store. |
It looks like "weird bug" is right. I loaded the extension from Github and the problem goes away. In fact I can toggle on and off the local extension vs the Web Store extension and the problem comes and goes with it! |
anything new ? still have the same bug if i use the normal release...currently using the beta but my browser tell me everytime that i shouldn't use it in developer mode. |
still the same bug. and the beta version somehow uninstalled itself. |
anything new? |
This is exactly the same thing I am experiencing. The menu continues to be broken. |
When I click the ScriptSafe icon, the dropdown menu does not fit within the dropdown window. I have to use the slider at the bottom of the window to see the whole thing. This does not happen with other add-ins. Very occasionally (but not usually) if I change the zoom level of the browser tab before I click the ScriptSafe icon, this problem goes away. I have attached a screenshot.
I am on Chrome (V 51.0.2704.79 m) on Windows 7, ScriptSafe V 1.0.7.4.
This seems similar to issue #7 but different enough I thought I wouldn't hijack that issue.
The text was updated successfully, but these errors were encountered: