mywot / chrome Goto Github PK

It would be convenient to have "Open WOT scorecard for example.com" in context menu when right-clicking on URL or selected portion of text.

Small and nice feature.

Inspired by: http://www.mywot.com/en/forum/20250-new-look-front-page

More smarter: check selection if there is something like hostname or url, and if not - don't show menu item.

When the addon starts first time with a browser, there are 2 errors in a console:

XMLHttpRequest cannot load http://www.mywot.com/setcookies.php?accessible=false&partner=&id=0b08........f24&nonce=bdf06...52779&auth=b0cac....387396e578c.
Origin chrome-extension://ihcnfeknmfflffeebijjfbhkmeehcihn is not allowed by Access-Control-Allow-Origin.

api.js:105
api.call.error: url = http://api.mywot.com/0.4/query?target=j%2BuVGOcNdLu5Q1fcB1Fw&id=0b0.......0d7d8f24&nonce=34271fcb...dc425&lang=ru-RU&version=chrome-20120220&auth=5ca46...f1bec75, status = timeout

(real hashes have been cut)

First error occurs every time when addon is loaded (browser started, addon reloaded). And the second one only after starting a browser.

http://www.mywot.com/en/forum/22844-wot-does-not-block-websites-with-a-very-poor-rating

Personally I agree with user:

A Google User, Feb 17, 2011
Would be nice to have a visual feedback when we rate a website using the extension, something like "Your rating as been uploaded". Also would be nice to be able to comment from the extension.

I'd like to have this feature too, or, have mywot.com/scorecard is opening extremely fast to leave a comment.

Any thoughts, why we didn't implement it yet?

As discussed in this thread, manifest_version will be required eventually and is recommended once Chrome 18 hits the stable channel:

https://groups.google.com/a/chromium.org/group/chromium-extensions/browse_thread/thread/d41e7eb74fd5de77/9e8a1289ade3c7cf

Changes to the manifest format are documented here:

http://code.google.com/chrome/extensions/dev/manifest.html#manifest_version
http://code.google.com/chrome/extensions/dev/manifest.html#content_security_policy

The default content_security_policy should be fine for us as we don't load scripts from outside the extension, but test to make sure nothing breaks.

actually, this is an issue for the Welcome Page, not for the addon...

It is not necessary to call that function twice.

All other code should be the same as in the master branch. The difference is only in manifest file.

There are tons of visits from different sites, provided by warning screen.

We need to know, where visits are from - rating window, warning screen, or smthng else.

There are some prepared funcs in firefox-xul repo to do this.

https://github.com/mywot/firefox-xul/blob/master/content/util.js#L207
https://github.com/mywot/firefox-xul/blob/master/content/commands.js#L447
https://github.com/mywot/firefox-xul/blob/master/content/warning.js#L617

The first step: make a list of possible sources, like a addon-warning, addon-rw-viewscorecard, ...

This is the same as mywot/safari#5 for Chrome (but this bug was hidden in Chrome).

files were sent by email.

Sami:
Warnings are injected to the page on all platforms except IE. This means the encoding used on the underlying website affects the warning overlay too. Our texts are all encoded in UTF-8, but if the website uses a different encoding, the warning texts can break, especially on languages that use multibyte characters (Russian, Chinese, Japanese, etc.).

Solution: Move the warning to an iframe, which covers the entire page, so the page doesn't mess up the layout or the encoding.

Sergey:

• not reproduced for http://shurik-sammy.chat.ru/ (Windows 1251, Chrome, Firefox)
• bug isn't reproduced on http://greentown.h1.ru with charset=windows-1251 in Chrome.
• I need some sample pages with non-utf8 encoding. Will find them first.

I need a way to change current language in addon when developing&testing.

I don't think it is required by users --> no need to show this on settings page. Something hidden will be enough.

It annoys me everytime.

Is it made intentionally?

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.

After WP will stop sending us settings, we can remove this piece of code.

as requested by MRU

This is a continuation of #16 - it would be better to see warning screen after some time after rating. For example - after 1 minute.

If addon is pre-installed to a browser, don't open welcome page on first start. Instead, show badge after some time (a day) to invite user to open welcome page.

Example:

content/search.js (302):

var r = data[0] && data[0].r ? data[0].r : -1;

There should be data[wot.default_component] instead of hardcoded [0].

Also check all occurences of such code.

User's request: http://www.mywot.com/en/forum/22256-special-color-and-or-icon-for-ignored-sites?comment=136692

Issue filed as a reminder.

I recently added a site to my ignore list (the site is technically safe, the but the company has a lousy corporate image, so it's rated red). Since the site is now ignored, I noticed my WOT icon is grey (and the text says 'ratings are not available').

I'm wondering if anyone has suggested that maybe a different color icon (blue?) could be used to distinguish ignored sites from sites which don't yet have enough ratings? I know there's also a question mark in the upper left quadrant of the icon for unknown sites, but that is not that easy to see. A totally different color would more clearly distinguish ignored sites from unknown sites.

Or even better (but harder to do) would be a 2-color icon. 1/2 blue (for the ignore) and 1/2 the normal website's color (so you're reminded about the site's WOT status). Or maybe keep the site's original color, but put a diagonal slash through the icon to show that it's being ignored (though that may end up looking too much like NoScript's icon!).

Personally, even for sites I consider safe, I don't mind the WOT icon color being red (in fact, that would still be useful), but having the fullscreen warning show up the first time I visit the site, and then have the 'top strip' WOT warning appear every time I navigate through the domain is what caused me to add the site to my ignore list in the first place. I just feel that now that I am ignoring the site, I no longer have any WOT information about the site (which would still be helpful to remind me that this site is still considered unsafe by some people, and I may want to rethink my settings from time to time).

permission error.

Refused to execute inline script because of Content-Security-Policy.
Refused to execute inline event handler because of Content-Security-Policy.

The addon should show a badge after some time from first launch of the addon (1 day? or 2 hours??)

Clicking on the button will open normal Rating Window with normal message in Russian like "Hi! You can rate sites using this tool"

This text is silly:

Просмотр подробных данных о рейтингах.
Добавьте свой комментарий.

(= view scorecard and comment)

When a site doesn't have a reputation, wot.geticon called from wot.search.getcss sometimes returns this URL:

chrome-extension://bhmmomiinigofkjcapegjjndpbikblnp/skin/fusion/16_16/plain/undefined.png

Apparently the r parameter is undefined, which results in an invalid URL and no rating icon next to the search result. How does this happen...?

Edit: Good news, I can't reproduce it. Seems to happen randomly.

We need to track amount of [active | registered] addons distributed by pre-installation.

Agreed with partner M to use 2 pre-setup values in the local storage:

embedded = true (if the addon was preinstalled in a browser; otherwise it will be undefined)
partner = "name of the partner" - we will use this param to count efficiency of partnership and amount of new/active add-ons.

We need:

1. check <if prefs.get("embedded") is set to true> during first run of the addon, and if so, don't show welcome page.

this will be a workaround until we have it implemented in Welcome Page (MRU customization).

Current one contains old homepage:
https://img.skitch.com/20120317-ryp3x8hatkpjh5ehexf2xd9fri.png

Users requested and I agree with them.

http://www.mywot.com/en/forum/25440-wot-add-on-should-signal-new-messages

It occurs in background.js in function setusermessage:

(obj.target == "all" || obj.target == "chrome") &&

small improvement.

The sample of fixed issue is here:

https://github.com/mywot/chrome/blob/master/content/search.js#L302

make it in both master and manifest-1 branches.

List of countries: http://en.wikipedia.org/wiki/Commonwealth_of_Independent_States#Economic_data

We have translations for ext_description, but they are not present in locales.

These are in Firefox, but not in Chrome, Opera, or Safari:

https://github.com/mywot/chrome/blob/master/_locales/de/messages.json#L72
https://github.com/mywot/chrome/blob/master/_locales/de/messages.json#L75

the commit is: b17c9be

When I see warning screen and intend to leave it, I have to point to small "close" icon on browser's tab. It takes time, and can be not so easy when > 10 tabs are open.

I'd like to have "leave this site" right on warning screen.

Probably, we need a prototype of design to discuss it.

What if we make a chrome page for a new tab like this (yandex visual bookmarks):

https://img.skitch.com/20120227-bjxcniqgr2k6m23pkreeyhnm4n.png

Packed with useful functionality this feature-page might be liked by users. WOT may get searches from it.

lets discuss.

bug report from a user:

When I scroll down on Google+, the Javascript profiler shows that 35% of the processing time is spent in chrome.extension.sendRequest.requestAnimationFrame. WOT's FireFox version doesn't have this issue.

https://chrome.google.com/webstore/support/bhmmomiinigofkjcapegjjndpbikblnp#bug

In case, when WOT doesn't have ratings for site, we can check current URL via Safe Browsing API (from Google/Yandex).

If SBAPI tell us, that url isn't safe - show warning screen.

Discuss.

Kate recommends to change it to this (lighter one):

webkit-linear-gradient(left, #DBDADA 0%, #F0F0F0 15%, #F4F4F4 50%, #F0F0F0 85%, #DBDADA 100%)

see details in internal wiki

The sample of fixed issue is here:

https://github.com/mywot/chrome/blob/master/content/search.js#L302

We are going to test new behavior of donuts in SERPs:

• Donuts are invisible by default;
• When cursor is over link or snippet, donut appears;
• When cursor is over donut, popup is shown (as it was before);

Need to mention

1. We need an "announcer" on the SERP, when user see it first time after deploying updated addon, to explain that addons works fine, but donuts were hid "for better UX".

note: probably, we aren't allowed to put announcer even.

Questions

1. What are the conditions of testing changes - language? % of new installations?
2. How shall we count "removing ratio"?