Opera 11.62 not working for www.spv.no and clanforge.multiplay.co.uk

Opera 11.62 not working for www.spv.no and clanforge.multiplay.co.uk

Hey.
The first problem is the bank Sparebanken Vest http://www.spv.no where there is impossible to log in to your bank account where this works perfectly in older builds of Opera.

The second page is http://clanforge.multiplay.co.uk where there are a frame on the right and another frame to the left where the menus are and when you click on Servers, profile etc the frame on the right wont change. This worked perfectly in older builds except 11.62.

I know this 2 sites will be hard to test since you need an account on both sites to test it. But its a major problem then needs to be fixed. I really want to downgrade my Opera for the time being. Is that possible?

-Best Regards
Stian

Have you tried deleting your cookies for those sites? That solves some problems.

I deleted all my cookies and also restarted my Opera and deleted all my cookies again and tried to login to both of those sites. And I am still having the same problem.


Link to the image
On the spv.no page this stays like this forever on trying to log in






Link to the image
And on the clanforge page this will always show the news even though i select Server or Profile etc

Having the same problem with using the net bank Sparebanken Vest.

It works with other browsers and, as previously said, it worked perfectly in older Opera versions too.

Hi,
does it solve these problems to use this user script?

http://files.myopera.com/hallvors/userjs/document_attachEvent.js

In 11.62 we've hidden the document.attachEvent method because having this method caused compatibility problems on certain important sites. I can easily believe that hiding it also causes compatibility issues..

(If you don't know how to install user javascripts, have a look at this guide: http://my.opera.com/operafan2006/blog/2007/02/13/how-to-install-user-java-script-in-opera . To run the script on the bank's website you probably need to go to opera:config#r%20j and turn on the "User JS on HTTPS" setting, then OK it when you load the first https page.)

Thanks a lot for letting me know whether this helps - it will help us understand the problem.

Originally posted by hallvors:

Hi,
does it solve these problems to use this user script?

http://files.myopera.com/hallvors/userjs/document_attachEvent.js

In 11.62 we've hidden the document.attachEvent method because having this method caused compatibility problems on certain important sites. I can easily believe that hiding it also causes compatibility issues..

Hi and thanks for your reply,

I can't answer for the second site mentioned by OP, but for spv.no: Yes, it does work again when using this user script

OK, colleague Yngve also uses this bank and share an error message. Thanks to you both, I'm about to ship a browser.js update that will make spv.no work in 11.62

Thank you very much
This script works perfectly on the bank site www.spv.no but I'm still having the same problem on the other page
http://clanforge.multiplay.co.uk :-/

Hm, is it possible to register a free account for testing with this site? Or could you send me any errors and/or a copy of the page, saved?

I saved the website here: http://dl.dropbox.com/u/69721925/clanforge.rar
I hope this will help. All the different pages seems to have .pl after instead of .htm or .php etc.

EDIT: I don't think there's possible to get a free account since it is a webpage for controlling a rented server from multiplay. So I think you will only get access if you rent a server there

Originally posted by SoidSnake:

I'm still having the same problem on the other page

Thanks for saving the files - it fails because we started hiding window.event. This code looks pretty old:

if ( window.event && window.event.srcElement && window.event.srcElement.href )
{
	// default the source object
	oSrc = window.event.srcElement;
}
else
{
	// reload the current page
	oSrc = document.getElementById( curTab );
}
}

sUrl = oSrc.href;

Could you please report a bug on this issue?

I did report it through the Opera menu -> Help - > Report a site problem..
if that helps?

Sorry, it would be better to report it at https://bugs.opera.com/wizard/ - and link to this thread

Okay. I have now posted the bug report Should I also report one on the www.spv.no site aswell?

Thanks! No report required for spv.no, I've already shipped a browser.js update for it.

Ok thats good So we can be using www.spv.no in the next update without the script then?

Yes, it should in fact be working already if the browser.js info page says your active file is from April 12 or later.

I see It works great now without the script

A bit on that matter:

I was wondering how "if (event)" can deliver a false value - as it does since the v11.62 update - although event.which or event.srcElement do deliver proper values.

  if ( window.event )
    output.innerHTML = "defined";             // "output" is just a debug div box.
  else
    output.innerHTML = "undefined: "+ [ window.event, window.event === undefined, typeof window.event, window.event.which, window.event.which === undefined ].join( " | " );

… delivers this line in an onKeyUp scenario:

undefined: [object KeyEvent] | true | undefined | 13 | false

Seems a bit illogical to me. Which is why, from my perspective, I don't understand why the code mentioned by hallvors is old. You prevent a runtime error of calling "uncertainObject.attribute" by making sure that the object is defined in the first place, before addressing its attributes. Yet, there is no alternative that I know how to make that check. Instead, these attributes (i.e. "event.which") can only be used by wholly omitting that check.

Doesn't seem like elegant programming to me.

Originally posted by WoodrowShigeru:

I was wondering how "if (event)" can deliver a false value

This is a magic hack for compatibility. The purpose is to make sites that do things like this start working:

if(window.event){
   // some IEish thing we don't support
}

and at the same time keep sites that do this working:

if( isOpera )element=event.srcElement;

or

if(!isMoz)element=event.srcElement;

or even just

var type=window.even.type

with no extra detection. It is illogical, but it makes a number of sites that otherwise wouldn't work, work.

Originally posted by WoodrowShigeru:

I don't understand why the code mentioned by hallvors is old

I'd call it old - or at least not well maintained - because it seems to have no usable alternative code for browsers that do not support window.event. More "modern" browsers and coding style don't support or discourage window.event and use the event object passed as an argument to the event listener instead.

Ah, I see. Thanks for clearing that up.