Examples don't work in IE9 #190

Open
pyjsorg opened this Issue Apr 27, 2012 · 2 comments

Projects

None yet

1 participant

Contributor
pyjsorg commented Apr 27, 2012

What steps will reproduce the problem?

  1. Use Internet Explorer 9 as your browser.
  2. Build the helloworld example, or visit http://pyjs.org/examples/helloworld/output/Hello.html
  3. It don't work :(

What is the expected output? What do you see instead?

Instead of the hellowworld demo, I get an error from IE9:

"Hello TypeError: Object doesn't support this property or method"

What version of Pyjamas are you using? which svn revision number?
On what operating system?

Pyjamas 0.7
Windows 7, Internet Explorer 9

If using PyJS, have you attached a javascript stack trace,
from IE's Script Debugger or from Firefox Venkman / Firebug?
Have you attached a stack trace from using "-d" compiler option?

If I type the following into the IE9 console:
window.frames[0].$pyjs.platform

I get:
"oldmoz"

Please provide any additional information below.

Possible solution:
In the file home.nocache.html, I added the lines:

else if (ua.indexOf('msie 9.0') != -1) {
return 'ie6';
}

After that, if I rebuild the demos they work in IE9. I don't know if this is ultimately the "correct" solution - hopefully someone with more knowledge of Pyjamas can take a look and verify this. I kind of suspect that it isn't quite right to stick with "ie6" as the user agent forever into the future, but I'm new here.

Original issue: http://code.google.com/p/pyjamas/issues/detail?id=529 (December 08, 2010 19:31:17)

Contributor
pyjsorg commented Apr 27, 2012

From cornelis...@gmail.com on February 22, 2011 18:03:08:
Ahhh. We probably should remove the download for 0.7. It's hopelessly outdated. Could you check if the error persists on the git checkout, or the snapshot from the git repository:

http://pyjamas.git.sourceforge.net/git/gitweb.cgi?p=pyjamas/pyjamas;a=snapshot;h=HEAD;sf=tgz

Contributor
pyjsorg commented Apr 27, 2012

From rich.new...@gmail.com on April 09, 2011 15:26:32:
This is now fixed with git commit 4f17793...

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment