by Christian Eyrich (Developer) on Jan. 29, 2011 · permalink

That’s unfortunate and I’d like to change this.
But please peppper and everyone else, if something’s not as expected I’d really appreciate a bit more informations.
I’ve e-mail too (see right column on the Add-ons page) where I can be contacted. Things that would be very helpful are where’s the problem exactly (no context menu entry?, no properties dialogue?, no data?, error message?), what other Add-ons you’ve installed, screenshot of the error, output from the Error Console and image you tried to get data from.

I’d like my extension to work on your system as much as you do but I definitely need your help there. Thanks.

by Christian Eyrich (Developer) on July 13, 2010 · permalink

Hm, some pages (at least the one for FxIF) on my site are dual language and can be switched (flag at the upper right corner of the page, as well as English should be the default for you anyway).

On the error: Yes, that’s a known bug which will be fixed for the 0.4.2. But I don't know when this will be released. You can mail me for a fixed version. My mail address is under the "E-mail your question" link on the FxIF page here at AMO.

by Christian Eyrich (Developer) on May 29, 2010 · permalink

Could you please give me more detail on the status bar question? You can mail me too.

The Esc key closes SeaMonkeys and Firefoxes (< 3.6) properties dialogue as it's closes the own EXIF dialogue in FF >= 3.6.

by Christian Eyrich (Developer) on May 19, 2010 · permalink

I think I'll add the software field into the next version of FxIF.

Regarding the field values in your comparison. The focus length is essentially the same, only FxIF's value isn't rounded and in addition gives a hint on which focal length a 35mm camera would have had to make the same image.
For the metering mode, it's the same but different namings. In the field of metering modes you might encounter quite a few different names for the same, there's no standard. Those names aren't taken from the image itself, there some field has a value of 1, 2, 3, 4, 5 a.s.o. which FxIF translates into human words.

by Christian Eyrich (Developer) on April 30, 2010 · permalink

As I replied to MuggelKid, the data you're missing has been removed in FF >= 3.6 by Mozilla. To add this back, please use Element Properties as I try to not make FxIF a solution for all problems.

by Christian Eyrich (Developer) on March 26, 2010 · permalink

I guess you're talking about using FxIF on Firefox >= 3.6 since in earlier versions and SeaMonkey it's embedded in the Properties dialogue anyways.

If I'm right, you might want to install Element Properties (https://addons.mozilla.org/de/firefox/addon/14228) with which FxIF cooperates well.
Else I'd appreciate more information on your environment and what you request.

by Christian Eyrich (Developer) on Feb. 27, 2010 · permalink

No, there's no way to write to photos using FxIF and there won't be in future. There is a lot software for editing image meta data but that's overkill for a browser extension I think.

by Christian Eyrich (Developer) on Feb. 27, 2010 · permalink

Do you mean while the extension is installed or while it's properties window is open?
Anyways, I did never notice some effect on image saving since using this extension. Does anyone else here noticed something like that?

by Christian Eyrich (Developer) on Feb. 15, 2010 · permalink

This might happen if there are only binary Exif data. Those are evaluated in the order they appear and the first one wins the trick.
This is a problem for some fields where there are alternatives which should have lower priorities. I now added some code for the next version so DateTimeOriginal will always have priority.
To test this for sure, please send me one of the problematic pictures.

by Christian Eyrich (Developer) on Feb. 7, 2010 · permalink

As promissed in my earlier reply, the just released 0.4 cooperates with the Element Properties extension.

by Christian Eyrich (Developer) on Jan. 29, 2010 · permalink

Thanks for bringing this up. This server sends even the images out as compressed (Content-Encoding: gzip) and when accessing the image from the browser cache directly it's handed to FxIF uncompressed which it can't handle.

I changed the code to not access the cache directly for now and hope this hasn't huge drawbacks. One drawback is that now any No-Cache statements from the server will be obeyed and the whole image refetched.
It will be as such in the forthcomming 0.4, but I'm still looking for alternatives.

by Christian Eyrich (Developer) on Jan. 16, 2010 · permalink

>have a Nikon D90 and the plugin says that the image is from a Nikon D60

Those informations aren't interpreted but contained in a string copied verbatim from the image. I've checked with some D90 images from flickr and FxIF always shows "D90".
But I'd be happy to check with your image if you could send it to me (you can also check it with some hex editor of other EXIF viewer).

by Christian Eyrich (Developer) on Jan. 10, 2010 · permalink

I just did for the forthecoming 0.4. But there are no values specified besides sRGB and semi-specified for AdobeRGB, so I don't know if that will help much.

by Christian Eyrich (Developer) on Jan. 10, 2010 · permalink

I didn't know this extension until now, thanks for the pointer. I'll have a look and experiment with it. If I succeed you'll get it with the forthecoming 0.4 of FxIF.