Justin Samuel

About me

Ontwikkelaarinligting
Naam Justin Samuel
Ligging Oakland, CA
Beroep Founder, FreedomCP
Tuisblad http://www.justinsamuel.com/
E-posadres
Gebruiker sedert July 10, 2008
Aantal byvoegings ontwikkel 1 byvoeging
Gemiddelde gradering van ontwikkelaar se byvoegings Rated 4 out of 5 stars

Bietjie meer detail...

My company, FreedomCP, makes a free hosting control panel.

More about me on Google+ https://plus.google.com/u/0/108182357943262548773

Byvoegings wat ek gemaak het

RequestPolicy

Be in control of which cross-site requests are allowed. Improve the privacy of your browsing by not letting other sites know your browsing habits. Secure yourself from Cross-Site Request Forgery (CSRF) and other attacks.

Rated 4 out of 5 stars (168)
132 526 gebruikers

My resensies

autocomplete popup resize

Has potential for people who need this functionality Rated 3 out of 5 stars

[Note: I was not a user of this extension. This review was submitted to provide examples to the AMO editors of how I would review addons.]

Mostly works on WinXP (Firefox 3.2pre1), but doesn't work well at all on Linux (Ubuntu 8.04, Firefox 3.0.5). With a bit more work it may become useful for more people.

Dié resensie is oor 'n vorige weergawe van dié byvoeging (1.6). 

iGoogle Tab Remover

Will meet the needs of users wanting to be rid of iGoogle's new tabs Rated 4 out of 5 stars

[Note: I was not a user of this extension. This review was submitted to provide examples to the AMO editors of how I would review addons.]

The extension works as described and does not cause side effects to non-intended websites.

Suggestions:
* Change the text in the Tools menu from "Enable/Disable iGoogle Remover" to "Enable/Disable iGoogle Tab Remover". As it is, it sounds like it should remove iGoogle completely in some way.
* Enable the extension to work on other iGoogle country TLDs when the new iGoogle interface goes live there. Currently the extension will only work for www.google.com.
* Future-proof the extension by making it not do anything if it doesn't detect the components of the iGoogle page that it expects to be there. That is, when a different version of iGoogle comes out that the extension won't work with, the extension shouldn't continue to affect the iGoogle page in any way (if possible).
* Clean up unused files packaged in the xpi and pieces of code/names leftover from extension template code.

The displaying of the iGoogle left tab when the blue box the extension adds is clicked could be improved. It is far from perfect and what is displayed does not work as well as the original iGoogle tabs do. I would consider the extension buggy because of this if it were not for the fact that my assumption is that people using this extension probably don't actually want to use the new iGoogle tabs at all, ever. I assume there is a cleaner way to do this so that it works smoothly and would cause people disliking Google's changes to iGoogle to exclaim "that's what Google should have done."

Regarding the categories this extension is listed in here on AMO, which are currently 1) Appearance, 2) Toolbars, and 3) Tabs: I don't see why this is in the Toolbars category. I also don't feel it fits in Tabs because Tabs refers to Tabs in the browser, not something called "tabs" by some web application's own interface. I know it's tempting to put it into as many categories as possible for exposure reasons, but sometimes it's inaccurate.

Dié resensie is oor 'n vorige weergawe van dié byvoeging (1.4).