Forum Moderators: open
First, as I mentioned months ago, there are occasions when Opera doesn't display an image, even though it has downloaded it. If I know an image is missing, then it's no problem. But I sometimes wonder what I'm missing.
On my own sites, it's always the same images that give the problem. It seems reporducible, but I cannot figure out what the telltale factor is.
Second, occasionally there is a link that will not change to "visited" colors, no matter what. Always the same link, and again, I can't see any telltale factors.
I had hopes for 6.03, but these still persist. I guess the new version was mostly about the security fix.
It's something with certain forms and Opera. I have several admin panels on some cgi scripts that I can only work with in IE not Opera. Same problem with a browser based email account I used to have.
These all have forms and don't get along with Opera.
When placing online orders I usually use IE also.
Brett suggested I try reducing the "maximum connections to a server" setting on Preferences > Network
Ya, some servers aren't setup to handle more than 6 simultaneous connections.
The Win2KPro version of IIS has a hardcoded limit of 10 connections.
I ran into this problem a lot when testing 4 browsers locally on IIS (MSIE, Mozilla, NS 4.x, and Opera). Now I know why -- my preferences in Opera were set to 8 connections.
It worked - thanks much!
I'd like to add "me too!"
Tedsters second question:
> Second, occasionally there is a link
> that will not change to "visited"
> colors, no matter what.
Is it a cgi form link? Or, the destination page is a secure page? Or the destintion page has "no cache" on it?
I'm not sure the qualifiers there, but I think if the destination page is uncacheable, then opera won't color the link.
Or, the page has visited set in css to the same as a link color? (css overrides user prefs - much to my dismay).
It's a straight HTML link, that also has onClick= code that launches the linked page as a pop-up for users that have JavaScript turned on.
In this case, there was a typo in the straight link URL, but not in the onClick code. So the link seemed to work, but the HTML link (with the typo) had never been accessed and naturally wasn't in the history.