Does what it says, but the cost is too high Bewertet mit 2 von 5 Sternen

Operator does just what it says it does, and is really useful for that. But unfortunately it has a huge cost in terms of performance. It's taken my a bit of investigation to pin it on Operator, but it seems it is responsible for really jumpy scrolling on long pages (Facebook newsfeed for example). The more I scroll, the worse it gets. I wonder if it's a blocking issue? As the page loads more posts the plugin is blocking rendering whilst is parses the new data? Whatever it is, sadly it basically makes Operator unsuable

Thanks for your comments. Unfortunately I just haven't had the time to make Operator better.

I'll probably be deprecating it soon.

Performance issues Bewertet mit 1 von 5 Sternen

The functionality of this addon is great, but the performance issues it creates make it unusable. It seems to me that the more tabs I have open, the slower the whole of my Firefox becomes.

Unfortunately just cannot recommend any longer.

I appreciate the feedback. Unfortunately this is one of those things that I simply don't have the time for anymore.

I should probably just remove it.

Video Issues Bewertet mit 1 von 5 Sternen

I had videos (youtube, and other sites) get all jumpy. After disabling and re-enabling different add-ons I figured out it was Operator causing this problem. Uninstalled and now no problems.

Bewertet mit 4 von 5 Sternen

Thanks for this plugin but i think something goes wrong when you export a photo to the vcard. I have a photo with in the src: data:IMAGE/JPG;BASE64,[...]And when you export the vcard file says:PHOTO;VALUE=uri:data:IMAGE/JPG;BASE64,[...]While it should be:PHOTO;TYPE=JPEG;ENCODING=BASE64:[...]What could be wrong here?

edit: I see outlook uses vCard version 3 and 2 of image implementation, while this plugin does version 4. Mmm ok.

Outlook export

To solve the outlook problem, I created a custom vcard 2.1 export available here:

Bewertet mit 5 von 5 Sternen

Excellent tool. This is one of the first add-ons I add after a fresh firefox installation in any Operating system.

Bewertet mit 4 von 5 Sternen

Cool add-on! Is hReview on the roadmap by chance?

Thanks for the kind words.

There's an hReview user script available here:

other languages Bewertet mit 3 von 5 Sternen

As many other users, i REALLY lack of multi-language support! Pls add it in next update! Otherwise, perfect tool...

Lack of International characters support Bewertet mit 3 von 5 Sternen

What about support for other languages? utf-8

Reloads page when switching tabs Bewertet mit 3 von 5 Sternen

I have also noticed that when Operator is installed there are performance issues switching tabs. It seems that when switching to a tab containing microformats, the plugin forces Firefox to reload the page (possibly multiple times for each microformat). But otherwise it's a very powerful and cool tool.

Causes major slowdowns Bewertet mit 1 von 5 Sternen

Normally it takes a fraction of a second to switch between tabs in Firefox, but if Operator is installed and the tab has heavy javascript, it takes 8+ seconds to switch between tabs and locks up the browser. It also conflicts with the RescueTime extension, making it extremely slow to Categorize Activities.

Unfortunately I have not had a chance to rewrite Operator to be more performant. As Firefox gets faster, Operator gets slower it seems.

Bewertet mit 3 von 5 Sternen

Thank's for the plugin.
Have 1 question - what about support for other languages. Look - I have site with russian content with microformats for address - when i click to find this address on google maps - I see this page - - seems there is problem with codding in plugin. I try it on different russian sites - the same problem.

Makes Context Menu Flicker Bewertet mit 1 von 5 Sternen

Add-on totally messes up context menu for me. I'm running Win 7 64-bit, FF 7.0.1, Firebug 1.8.3 and a few other addons.

Bewertet mit 2 von 5 Sternen

It does what it's supposed to do but it incredibly slows down my whole Firefox, especially switching to panels with some heavy page. I disabled all settings which were marked that they could affect performance but it didn't help. So bye bye. (Firefox 6, Linux)

I'm sorry your seeing this. Unfortunately with later versions of Firefox, things have gotten slower and slower.

It's in dire need of a rewrite, but I don't have time.

Bewertet mit 4 von 5 Sternen

Very useful for the older semantic markup supported. Really needs the new 2011 HTML microdata supported! Without this this addon isn't going to be of much use going forward as more web sites converge on the new standard.

See for a site which live extracts HTML5 metadata. You can get the javascript source for that site from

You can turn off the toolbar and use other mechanisms to access the different microformats. You can use a toolbar button, the URL bar or a status bar icon.

We're looking at microdata in the future.

Bewertet mit 5 von 5 Sternen

a good idea "Operator lets you combine pieces of information on Web sites with applications in ways that are useful. For instance, Flickr + Google Maps, Upcoming + Google Calendar, Yahoo! Local + your address book, and many more possibilities and permutations."

brought into my mind the the idea of "borrowing" already running applications results from wwweb and bringing them into virtual operating systems and from there to our terminals ..

unfortunately after the installation i discovered a GREY (turned off) status bar button and a a similar toolbar ... perhaps not installed when using some personas or without repeated restart

and no manual guide "click and discover" for how to make your add on useful to anyone who doesn't know "how to"

is very possible that your add on doesn't work anymore
however for its huge potential is on my list of great add ons for Firefox

Bewertet mit 4 von 5 Sternen

Just a little lack.
It shoudl be nice to integrate the following hack (written in French) to enable OpenStreetMap :

Dupliquer google.js
Dans l'archive, trouver le fichier ./content/SemanticActions/google.js
Le copier sous le nom ./content/SemanticActions/openstreetmap.js

Modifier openstreetmap.js
Ouvrir le fichier ./content/SemanticActions/openstreetmap.js avec l'éditeur de votre choix

Voici les modifications à apporter au fichier.
ligne 3
- var google_maps = {
+ var osm_maps = {

ligne 4
- description: "Find with Google Maps",
+ description: "Find with OpenStreetMap",

ligne 5
- shortDescription: "Google Maps",
+ shortDescription: "OpenStreetMap",

ligne 6
- icon: "",
+ icon: "",

ligne 26
- return "" + Microformats.simpleEscape(semanticObject.label[propertyIndex]);
+ return "" + Microformats.simpleEscape(semanticObject.label[propertyIndex]);

ligne 32
- url = "";
+ url = "";

ligne 61
- url = "" + semanticObject.latitude + "," + semanticObject.longitude + "&q=" + semanticObject.latitude + "," + semanticObject.longitude;
+ url = "" + semanticObject.latitude + "&mlon=" + semanticObject.longitude + "&layers=B000FTF";

ligne 62, suppression
- url += " (" + semanticObject.toString().replace("(", "[").replace(")", "]") + ")";

ligne 69 (68)
- var google_search = {
+ var osm_search = {

ligne 70 (69)
- description: "Find with Google Search",
+ description: "Find with Nominatim",

ligne 71 (70)
- shortDescription: "Google Search",
+ shortDescription: "Nominatim",

ligne 72 (71)
- icon: "",
+ icon: "",

ligne 79 (78)
- var property = google_search.scope.semantic[semanticObjectType];
+ var property = osm_search.scope.semantic[semanticObjectType];

ligne 87 (86)
- return "" + encodeURIComponent(searchstring);
+ return "" + encodeURIComponent(searchstring);

lignes 93-238 (92-237) suppression

ligne 240 (92)
- SemanticActions.add("google_maps", google_maps);
+ SemanticActions.add("osm_maps", osm_maps);

ligne 241 (93)
- SemanticActions.add("google_search", google_search);
+ SemanticActions.add("osm_search", osm_search);

ligne 242 (94) suppression
-SemanticActions.add("google_calendar", google_calendar);


Compléter SemanticActions.js
Ouvrir le fichier ./content/SemanticActions/SemanticActions.js avec l'éditeur de votre choix

ligne 37, ajout
+ ojl.loadSubScript(baseurl + "openstreetmap.js");

Diese Bewertung wurde für eine vorherige Version des Add-ons ( abgegeben. 

Bewertet mit 4 von 5 Sternen

One of my new favorite extensions.

Diese Bewertung wurde für eine vorherige Version des Add-ons ( abgegeben. 

Bewertet mit 4 von 5 Sternen

very nice tool. works even with dynamically produced vcard from ajax-loaded data.
but is there no way to disable this huge operator-toolbar? i would like to use only the buttons, the "autohide" option is not subtile enough...

thank you!

Diese Bewertung wurde für eine vorherige Version des Add-ons ( abgegeben. 

Bewertet mit 2 von 5 Sternen

This is a nice tool, but on pages with 100 or more hCards, for example, the tool bogs down page loading and rendering immensely. An instant disable option would be nice -- at least until performance issues can be addressed.

Diese Bewertung wurde für eine vorherige Version des Add-ons ( abgegeben. 

Bewertet mit 4 von 5 Sternen

I think the basic idea of microformats is solid, but still developing, so some of my issues might be with the format rather than with the add-on. Here are the things I noticed and thought needed improving:

* If I export as vcard, the exported file is called "hcard.vcf", which isn't very helpful and can cause file overwrite issues. It ought to take the fn as the title.

* If I don't set an fn class, but only use the given-name and family name classes, the Operator toolbar doesn't light up. fn should be optional, otherwise I'm forced to hide the redundant element(s).

* If I use the "dtstart" and "dtend" classes in anything other than a abbr element, operator doesn't light up for events. Since my page is a schedule, and the schedule is (appropriately) set up in a table, it seems redundant to set the same data in an abbr element when I could just set the dtstart to the table cell.

* If I add a single event to my Google Calendar, I'm redirected to Google Calendar in the same tab, so I lose the page I'm on. At the very least, a new tab should open, but ideally I should be able to choose the location of my gcalendar as an option and not have to do anything at the Google Calendar site (not sure if that's a gcal option).

* If I have a page with a dozen events, I can export the entire calendar as an ics file. It would be nice if I could rename it something other than hcalendar.ics (maybe the suggested title could be a class, like class="hcalendar venue_cal_concerts", or something) or the user could choose the title. It would also be nice if instead of exporting it and then reimporting it to gcal, if I could "add all to Google Calendar".

I know the developer is in need of financial support to get back to this project, so I'm not expecting overnight implementation, but all of these seem fairly natural improvements, assuming they can be done at the add-on level.

Diese Bewertung wurde für eine vorherige Version des Add-ons ( abgegeben. 

Thanks for the comments

Thanks for your thorough comments

Let me go through them in order:

1. Good request. I'll do that.
2. This is part of the spec right now. We're working to get that changed to the next rev of hCard.
3. I believe this is being worked on as part of a new spec for setting dtend/dtstart. I'll be integrating that soon. An example page would be really helpful.
4. I think if you hold down the shift key, it opens a new tab, but I should make opening a new tab the default behavior. I'll check on that.
5. As far as the name goes, I'll look at a way to actually set the name. As far as Google Calendar goes, I haven't found a good way to import multiple events into Google Calendar. I'll keep looking.

As far as the financial support goes, yes this isn't my fulltime job so I am looking for that. My plan is that as I get Contributions to the project, I'll start adding it into my schedule. So my first work should start happening next week.