i think the old one was better.. :/
dont you think so?!
besides the upper side of the screen.. (they needed to change it) |
Ionut > since a week ago :)
http://www.zorgloob.com/2006/06/nouveau-look-pour-les-serp-de-google.asp
They remove the "Play" button on the small screenshots in order to incite visitors to watch the entire video. |
The change they really ought to focus on is to index web video content as well. OK, so many videos might not be of good quality – but at least make it an additional search result, lower-ranked if needed. |
This thread looks really bad in Opera 8.52 and Opera 9 Beta 2 (so, I'll conclude it looks bad in Opera) because of the image. The text expands beyond the right border. |
And IE too. And not just this thread, every thread that has an image whose width > 490px. The JS code doesn't work this way. |
The resize should take place in body onload. |
Doesn't onload trigger only after all images have been loaded, which would be too late? I'll switch back to CSS in the meantime. |
You could always add the onload event to the IMG tag. That way, when the image has finished loading (rather than the entire page) it *should* resize correctly. I think this was the problem with IE and Opera before – they were calling the JS before the image had loaded.
(The problem with using CSS like you are doing means that any smaller images are over-sized – but I assume you knew that already...) |
Let's use two threads.
http://blogoscoped.com/forum/38459.html
< 490px
http://blogoscoped.com/forum/38764.html
> 490px (this one)
IE7 displays them the same as Opera. The images keep their size. |
> The problem with using CSS like you are
> doing means that any smaller images are over-sized
In Firefox, smaller images keep their size (I'm using max-width, but only FF seems to "get" this).
I checked Ionut's suggestion he sent yesterday and now I understand why it worked the way it did – there was a "visibility: hidden" for the images until the onload was called. I think onload is only "allowed" for the body element (by W3C) so I'll give that another try soon. |
