Open sorgoz opened 12 years ago
From feedback:
A Google User May 24, 2010 i want it to be able to block the untrustworthy websites.. what good does the warning do if there is a virus being installed in the background while i'm on the warning screen?
Tested permissions' trap - we can freely add new permissions for blocking/request manipulation feature (no auto-disabling in this case):
"permissions": [
"tabs",
"http://www.mywot.com/*",
"http://api.mywot.com/*",
"https://api.mywot.com/*",
"http://*/*",
"https://*/*",
"webRequest",
"webRequestBlocking",
]
extending permissions that way requires manual review from google when published via Dev Deshboard.
I've completed this story by signing agreement and now, my test addon is published (for testers only). It had the same permissions and content-scripts matches as WOT addon has. And then, I extended permissions.
New version with extended permissions was installed silently without any questions to user.
So, we can do this way. Just need to sign agreement with google.
One more request from user: https://www.mywot.com/en/forum/21448-wot-blocking-chrome
When I use Firefox WOT blocks sites so my kids can't access. With Chrome it identifies the site but does not block access. How can I make Chrome safe too?
I feel I'm on a right way :)
+1 feedback about "block" feature: http://www.mywot.com/en/forum/30762-thank-you-wot
For most reasons of why I'm still using WOT, is even though some WOT ratings are what I think are incorrect, the addon puts the users ratings before WOT's ratings, and if you have "Block" on and you rate the site poor or very poor, it will shield you from the sites content whether it be pictures, or scripts or even viruses. I enjoy this factor. Keep up the good work.
The WebRequest API allows to make syncronous WOT API call before loading site.
http://code.google.com/chrome/extensions/webRequest.html
And it seems that adding the "webRequestBlocking" permission doesn't disable addon as this permission doesn't show warning http://code.google.com/chrome/extensions/permission_warnings.html
Needs to check it, and if this assumption is true, then put this feature into a roadmap.