-
Notifications
You must be signed in to change notification settings - Fork 80
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
ANNOUNCEMENT: Changes to Updates #29
Comments
I am guessing sods law has struck here, with this urgent update been slower than usual for the webstore to update. End of the day you do this for free, and I respect that hence there is no justification for people been rude to you, the error happened, but you have already said you will react in future to lower the chances of it again. this is good :) So thank you for this excellent extension and yes the browser does feel faster to use now. |
@chrcoluk I appreciate it! Everyone, as promised I will be pushing updates to the Chrome Web Store much less frequently. This repository will always have the latest code updates and can be downloaded/synced at any time. It can be considered to be stable as whatever is synced on here is what I'm personally running. But if you still want to disable the update notifications, here are steps:
Note: if you disable this option ScriptSafe will still wait for a complete browser restart before updating itself (to not interrupt your current browsing session). By disabling the above option, you won't know whether or not there's an update for ScriptSafe available. |
From this point on I will be posting beta releases here for testing and feedback before pushing them to the Chrome Web Store. v1.0.7.11 beta is available for testing: more info here - #40 |
Thanks for all the work! |
Thanks Andrew for ScriptSafe and for the dedication to your users. |
The update notification was completely removed in v1.0.7.11 and I feel things are stable in v1.0.7.12 (which addressed two important issues and was tested + confirmed by the issue reporters). Development will continue here, and updates (most likely just enhancements) will be pushed to the Web Store when needed/well-tested. We've come a long way; I realize there were a lot of releases over the two weeks and just wanted to again thank everyone for sticking around and using ScriptSafe :) |
I just wanted to make an announcement regarding updates:
Respect Same-Domain Issue (Respect Same-Domain issues #25): this is one of the bigger issues that I addressed in an update (v1.0.7.8) I uploaded to the Chrome Web Store at 8:45pm eastern yesterday (Sunday, June 5). Ever since it has been in a "Pending Review" status, meaning someone at Google needs to manually approve it before it is pushed out to users. I've just contacted the Chrome Web Store to inquire about the review status and that it is quite an important update.v1.0.7.8 was manually approved and published 26 hours later by Google.Moving forward, you can expect the following:
Thanks.
The text was updated successfully, but these errors were encountered: