Na bitte, mittlerweile, d. h. schon seit 14.2., ist das Problem dem Opera-Entwicklerteam bekannt.
_______________
All Opera x86 builds seem to have a large flaw - no direct internet access!
I decided to post this here as the Beta testing forum isn't particularly useful for Mac users. Basically, I have an Intel iMac, and based on the (one) person I've found with another Intel iMac's testing, I've come to the conclusion that there is some sort of big problem when Opera is run as native x86 code - it can't access the internet!
Out of the box, if you run Opera TP1, TP2, or the latest weekly build, it will fail to contact any server you point it to, only load and load and load. If it is opened in Rosetta, it will work, however this is unfavourable as Rosetta is pretty unacceptably slow. This behaviour has occured for me and the person I had test it.
The workaround: Set up a proxy server. I went to the trouble of downloading Darwin Ports and installing an Intel version of Squid, and by accessing the internet through the local proxy Opera works - however, for reasons that are too complex for me to figure out, often I get stupid delays and have to refresh pages when they are loading because either Opera is not accessing the proxy efficiently, Squid is not set up correctly, or there is a bug in OS X. I have tried using Privoxy instead of Squid, there is no real difference. I have also tried deleting my Opera preferences and starting afresh, no difference.
I would like to know if anyone can figure out what might be preventing Opera from working. I have been told by one Opera developer in the IRC chatroom that in his experience this problem does not exist on Intel Macs - and I can't believe that two post-Macworld builds have been tested and released with this as an unavoidable problem! If anyone with an Intel Mac can confirm this in the thread, I would very much like to know about it - if it's something endemic, I'll report it as a bug.
http://my.opera.com/community/forums/topic.dml?id=124752
_______________
