Shadow bug

[Juul]

Wanted to report a bug for the background shadows of images. When using this for big images, it won't work, because background size is only 118x118px

background:url("/components/com_phocagallery/assets/images/shadow1.gif") no-repeat scroll 50% 50% transparent

-edit-
Ok it's because I later on edited the image sizes. Apparently Phoca already created a background image. But that should be corrected I think. Don't know how to use bigger images with shadows (inserting everything again is not really an option).

Plugin simple image gallery extended (SIGE) uses a big shadow that is alligned properly. Maybe a good solution, then this is also not needed:
https://www.phoca.cz/documents/2-phoca-g ... w-resizing

[Jan]

Hi, see:
https://www.phoca.cz/documents/2-phoca-g ... ound-image
Fixed image is used because of performance issue (instead of 4 divs by every displayed thumbnail)

This will be not more needed in days all used browsers (include IE) will support CSS3 and shadows attributes.

Jan

[Juul]

Hi Jan,

Its possible with one background image and a border:
http://www.mapito.nl/portfolio/moodboards

If you delete the table and uses span/div I don't think you'll need more divs/spans then you do now with tables. The filesize of the large background image is quite small.

>>This will be not more needed in days all used browsers (include IE) will support CSS3 and shadows attributes.
Yes thank god, but that'll take some years (some people are still using IE6 for example).

Maybe an idea? Would make it more userfriendly

[Jan]

Hi, in this forum I have explained it - because of different browsers (include IE 6 - 9) very complicated system for displaying images centered vertical and horizontal is used - this is why the background images is used for displaying shadows.

Jan

[Juul]

Hi Jan,

Maybe the mapito link with SIGE also works in these browsers?
I don't know. I respect your choice and thanks for this nice component

Regards,
Juul

[Jan]

Hi, , yes the advantage is, you are independent on my choice because the component is written in MVC and can be easily customized (without depency to upgrades)

Jan