asbo Posted May 3, 2010 Report Share Posted May 3, 2010 A couple (at least) of these have sprung up, for no apparently reason. If you click them, the light-box version is sized normally. (Win7 x86, FF 3.6.3) Link to comment
Shaun Hayward Posted May 12, 2010 Report Share Posted May 12, 2010 Yet another casualty: Link to comment
jgcode Posted May 14, 2010 Report Share Posted May 14, 2010 Ok, I have been seeing this for a while. In PMs and now posting. Glad? to see others have same problem (hey - at least that means I am not alone!) Mods Is this an IPB Known Issue? Is there a workaround? Cheers -JG Link to comment
Francois Normandin Posted May 17, 2010 Report Share Posted May 17, 2010 A workaround: it seems that any picture that has a width of at least 500 pixels is displayed well. 1 Link to comment
jgcode Posted May 18, 2010 Report Share Posted May 18, 2010 A workaround: it seems that any picture that has a width of at least 500 pixels is displayed well. How many pixel incrementations did it take to figure that one out! Good Job Link to comment
Francois Normandin Posted May 18, 2010 Report Share Posted May 18, 2010 Nothing too fancy: I used a standard genetic optimisation algorithm... (I uploaded 5 or 6 images) Link to comment
silmaril Posted May 19, 2010 Report Share Posted May 19, 2010 (edited) Another victim: http://lavag.org/top...llback-vi-type/ The HTML source code is very clear in this aspect: the image is sized to 500x1000 pixels: <a class='resized_img' rel='lightbox[74494]' id='ipb-attach-url-2273-1274272465-42' href="http://lavag.org/ind...;attach_id=2273" title="Register_Events_Problem.png - Size: 14.95K, Downloads: 5"><img src="http://lavag.org/upl...31269_thumb.png" id='ipb-attach-img-2273-1274272465-42' style='width:500;height:1000' class='attach' width="500" height="1000" alt="Attached Image" /></a> Ergo: This behaviour is definitively caused by the forum software, not by the browser. Edited May 19, 2010 by silmaril Link to comment
Michael Aivaliotis Posted May 28, 2010 Report Share Posted May 28, 2010 This issue is now resolved. 1 Link to comment
Recommended Posts