Same size on my screen, you sure you havn’t perhaps adjusted the browser font size by mistake?
Thanks – indeed, it seems to be a browser issue. fmueller.com looks fine in IE and Opera, but not so good in Firefox. Especially the fact that images in the slideshow appear cropped in Firefox is vexing. I think I recently upgraded to the latest version of Firefox (3.0.8). Maybe there is a compatibility issue?
Frank
Both sites use font-sizes specified in ems. This is a relative font-size that uses the browser base text size (set in your individual browser configuration) and then applies the factor defined in your CSS. So a CSS font-size of 1.5em will result in a final text size that is equal to your base font size x 1.5.
Chances are that you have different base fonts/sizes in IE compared to FF – which accounts for the text size variation that you’re currently seeing. It’s definitely not a compatibility issue. In fact, I always recommend using Firefox as the yardstick and then making adjustments via conditional CSS for IE. The former is a more standards-compliant browser.
images in the slideshow appear cropped in Firefox is vexing
I didn’t see any cropping. If this is still a problem, could you post a sample url?
Thanks for the explanation regarding the font issue. I can live with that, and will probably make the font a bit bigger to make it look perfect in FF. Not so worried about IE 😉
Regarding the cropping, the bottom right corner of all images in missing of all slideshow images when the site is viewed using FF:
[img]http://www.fmueller.com/images/cropping-problem-ff.jpg[/img]
Viewed with IE
[img]http://www.fmueller.com/images/cropping-problem-ff.jpg[/img]
Viewed with FF – note the missing bottom, right corner of the image.
Is this cropping only happening with flash files? Is NextGen Gallery creating these from static images (sorry – I’m not familiar with this plugin)?
Looking at the screen shots, it’s not so much a cropping problem as the fact that FF and IE can’t seem to agree as to what size some of the embedded graphics should be. The “cropped” FF version actually looks like a larger image that is being truncated by the width and height parameters of the object tag. That makes me think that the problem is within the slideshow file and/or its generation.
My best guess is that FF is trying to do the “right thing” whilst IE is applying an automatic re-size. The latter’s performance with the <object> tag is rather patchy and unpredictable.
Two thoughts:
– it’s an issue with the plugin’s slideshow generation
or
– when you created the slideshow, you used images with varying sizes and some of the images are slightly larger than the specified size of the final Flash object.
It might be worth flagging this up with the plugin’s author.
Yes, NextGen is creating a slide show (or gallery) from a folder containing a number of static jpg images. Its a very popular plugin, and highly customizable. The images I am using for the front page slide show are 490px X 300px. Images I use for slide shows on other pages are mostly 800px X 533px. The display size is 450px X 280px. I have set this latter size as ‘default size’ under gallery/options/slideshow as well as in the tag used for the slideshow:
[slideshow=2,450,280]
As far as I know, the re-sizing for the slide show should be controlled by a parameter ‘stretch image’ under gallery/options/slideshow. This parameter can be set to true, false, fit, and none. So far I had it set to ‘true’, but I just tried out all four values, and it has no effect on the look of the slide show in either FF or IE.
Contacting the plugin author might be a good idea!
Many thanks
Frank
I should also say that until recently the site with the images in question and the slideshow created by the NextGen plugin looked just like I wanted it to look in FF. The problem has only recently arisen, and I think the only variable is a new version of FF I am using.
I just fired up my old computer which sits around unused and still has FF 3.0.1 installed. The site displays perfectly on that machine. So the issue is clearly with FF 3.0.8. I’ll make the plugin author aware of it and see what can be done.
Greetings
Frank
