My OperaYou need to be logged in to post in the forums. If you do not have an account, please sign up first.
BIG images seem to redraw
As the title says. When loading hi-rez images it looks like Opera is re-drawing the image after it is loaded.An example...
http://clanfru.com/gallery.php?cid=22
Click on any of the images in this gallery. I know there is Javascript involved in this example but i have noticed the same effect on images alone as well.
Anyone got a solution? I tried fiddling about with the Preferences » Advanced » Browsing » Loading to (e.g setting it to "redraw instantly" etc.). Didn't help..
Ohh. I am using the latest version (Opera 10.52).
By the way the latest version is 10.53 Perhaps you could upgrade to that and see if it solves your problem.
Be helpful to the shyman, and be wary of the slyman.
Be guidance to the blindman, and be thankful to the kindman.
ʎzzıp ʇǝƃ llıʍ noʎ ʇıq sıɥʇ pɐǝɹ ʇ,uop
I have a hunch that it may be an opacity issue instead, though. In my case I call element.fade('in') (using MooTools) to show the image. On the site linked to in the OP I could only replicate the issue by closing the image, which fades it out (after it vanishes then reappears temporarily).
Originally posted by Frenzie:
There's the 10.5x problem that images seem to stop displaying that they're loading at about 1/5th of the image and they don't show up any more until they're finished loading completely.
FWIW, just couple of days ago I had similar experience with 10.10 (IIRC, not the first time). I had "supersurfed"
with Opera for a while and Opera began to act flaky (check Opera misbehaves with ~100+ tabs for reference) and didn't show many images at all, some pages sometimes didn't render properly though fully loaded, etc. memory/resource leak/allocating/whatever problems. Some images started to load when reloaded, but only showed a small part of the top image until the whole image was loaded. 10.5x _might_ be even more flaky.. there's abundance of 100% CPU / RAM / "resource" problems reported here already.Originally posted by benryves:
I've encountered a similar problem myself with a lightbox script I wrote (possibly?) You can preview it here (click the thumbnail at the top of the page). When the large image has been added to the page it briefly vanishes then reappears with an annoying flash. Older versions of Opera didn't do this, and other browsers aren't afflicted.
I have a hunch that it may be an opacity issue instead, though. In my case I call element.fade('in') (using MooTools) to show the image. On the site linked to in the OP I could only replicate the issue by closing the image, which fades it out (after it vanishes then reappears temporarily).
I guess this is the problem. The lightbox script is fading in... anyone knows how to make a nice fade-in effect for Opera??
Originally posted by mw2:
The lightbox script is fading in... anyone knows how to make a nice fade-in effect for Opera??
Same way you do in Gecko and Webkit: -o-transition:.1s; -webkit-transition:.1s; -moz-transition:.1s;
Originally posted by natural-kutkaa:
I had "supersurfed"
I would rephrase that as it _IS_ more flaky.
But ftr, this problem occurs on a clean install with just one tab as well, so this image loading thing is really an inherent problem. If I open this image in 10.10 it loads properly (unless there's over a 100 tabs, apparently
) and in 10.5x it never does.Originally posted by Frenzie:
I would rephrase that as it _IS_ more flaky.
Heh, I was too careful what I say around here, you know, some "entities" don't like "absolute" accusations.
Originally posted by Frenzie:
his problem occurs on a clean install with just one tab as well, so this image loading thing is really an inherent problem.
Oh, ok, that's bad. Has it been reported?
Originally posted by Frenzie:
(unless there's over a 100 tabs, apparently
Though, it's about "many" tabs, not necessarily near or over 100 tabs only... I've to confess that I don't like that topic title, it might give wrong ideas. The problem is rather about many sites/tabs opened in a long session running Opera.. that builds up the memory/resource leakage (or whatever the problem is).. though you need _some_ tabs to notice it, I'll confess that. But, going OT...