Opened 13 years ago

Closed 13 years ago

Last modified 12 years ago

#998 closed defect (fixed)

DEBUG: dojo.widget.Parse: error: [Error: Not implemented] with Eclipse internal web browser

Reported by: anonymous Owned by: Adam Peller
Priority: high Milestone:
Component: Widgets Version: 0.3
Keywords: Cc:
Blocked By: Blocking:

Description

I just started using tabs with dojo in Eclipse 3.1.2, but I always get DEBUG: dojo.widget.Parse: error: [Error: Not implemented] after my first Tab is rendered (the actual contents of the tab are however still missing, and the second tab shows up un-rendered as contents in the first).

When I try with either IE or FF outside of Eclipse it works fine, so it is related to the build in browser of Eclipse. This is however the first time that something doesn't work, and it is annoying for development.

Attachments (1)

eclipse.patch (651 bytes) - added by Adam Peller 13 years ago.
workaround for window.external failing inside IE in Eclipse

Download all attachments as: .zip

Change History (15)

comment:1 Changed 13 years ago by adam@…

If you happen to visit this bug again, please add an e-mail address so you can be contacted for more details. What version of Dojo was used and can you provide an example? How was the application launched/deployed? The browser in Eclipse is essentially the same as Firefox 1.5 so it's unusual to see any differences.

comment:2 Changed 13 years ago by adam@…

Also, which internal web browser was used? (There are at least 4 different impls!) It depends on your platform, how you launched the browser, and whether or not the AJAX Toolkit Framework (ATF) was installed...

comment:3 Changed 13 years ago by guest

The browser is the internal one as you get when you do a "Run on server" in Eclipse for a Java J2EE project (I don't know anything about 4 different implementations). I just took some Javascript from the web which returns the following information (I hope it is usefull) when executed via the internal browser;

JavaScript? Browser Sniffer

Navigator Object Data
navigator.appCodeName: Mozilla
navigator.appName: Microsoft Internet Explorer
navigator.appVersion: 4.0 (compatible; MSIE 6.0; Windows NT 5.1; SV1; .NET CLR 2.0.50727)
navigator.userAgent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; SV1; .NET CLR 2.0.50727)
navigator.platform: Win32
navigator.javaEnabled(): true

Version Number
major version number: 6
major/minor version number: 6

Browser Version
nav:false
nav2:false
nav3:false
nav4:false
nav4up:false
nav5:false
nav5up:false
nav6:false
nav6up:false
nav7:false
nav7up:false
nav8:false
nav8up:false

ie:true
ie3:false
ie4:false
ie4up:true
ie5:false
ie5up:true
ie5_5:false
ie5_5up:true
ie6:true
ie6up:true

aol:false
aol3:false
aol4:false
aol5:false
aol6:false
aol7:false
aol8:false

opera:false
opera2:false
opera3:false
opera4:false
opera5:false
opera5up:false
opera6:false
opera6up:false
opera7:false
opera7up:false

safari:false

konqueror:false

Gecko based: false

mozilla (guessing): false

firebird: false

firefox: false

webtv:false

hotjava:false
hotjava3:false
hotjava3up:false

AOL TV(TVNavigator):false

JavaScript? Version
js:1.3

IE 4/5/6 Script Engines Installed: JScript
Version: 5.6.8820

OS
win:true
os2:false
mac:false
unix:false
sun:false
irix:false
hpux:false
aix:false
linux:false
sco:false
unixware:false
mpras:false
reliant:false
dec:false
sinix:false
bsd:false
freebsd:false
vms:false

Object Detection Tests
document.all: true
document.anchors: true
document.cookie: true
document.forms: true
document.getElementById: true*
document.getElementsByTagName: true
document.documentElement: true
document.images: true
document.layers: false - NS6 gives false here
document.links: true

window.frames: true
window.length: 0

Method Detection Tests
window.RegExp?: true
window.Option: true

Screen Properties
window.screen: true
screen.height: 1024
screen.width: 1280
screen.availHeight: 994
screen.availWidth: 1280
screen.colorDepth: 32
fontSmoothingEnabled: true

Document Properties
document.URL: http://localhost:8080/DojoTest/browser.jsp[[BR]]

Flash Detection
Flash Player Present: true
Player Version: 8

comment:4 Changed 13 years ago by guest

The DOJO version I downloaded is "dojo-0.3.1-ajax.zip"

Don't ask me why I picked that one (basically I only need tabs, datepickers and maybe some AJAX stuff).

You can reach me at; paul underscore nicolay at msp dot be

comment:5 Changed 13 years ago by dylan

Milestone: 0.6

comment:6 Changed 13 years ago by dylan

Owner: changed from anonymous to Adam Peller

comment:7 Changed 13 years ago by Adam Peller

Bizarre. This is basically IE6 embedded in Eclipse and may need to be pursued as an Eclipse.org bug, but let's try to narrow down the problem. I'll contact the reporter and see if we can get an example.

Changed 13 years ago by Adam Peller

Attachment: eclipse.patch added

workaround for window.external failing inside IE in Eclipse

comment:8 Changed 13 years ago by Adam Peller

Okay, I tracked it down, without an IE debugger (finding exception throws is particularly painful without a debugger!) The error came from dojo.lang.nameAnonFunc() which simply tries to iterate through properties on the Window object and reference them:

for(var x in nso){

if(nso[x] === anonFuncPtr){ ...

where nso is a Window. Strangely, Window.external throws an exception when in IE in Eclipse -- almost certainly a bug in Eclipse's IE integration, which I will report. The workaround is to surround this with a conditional or try block -- I prefer the latter, but I'm not thrilled with putting in the patch just to workaround an Eclipse bug. Thoughts? Guess we can take it out after Eclipse fixes it?

Note that this is the default Eclipse web browser on Windows, which uses their own code to embed IE. The bug will not be seen on other platforms where Eclipse uses other browsers, nor will it be a problem once Eclipse lets you choose a browser other than IE, which I think is the long-term plan.

comment:9 Changed 13 years ago by Adam Peller

p.s. the bug can be reproduced simply by bringing up the embedded IE browser in Eclipse and browsing to tests/widget/test_TabContainer.html

comment:10 Changed 13 years ago by bill

Detective Peller - Yeah it's annoying to have to add try/catch but it seems like the lesser of two evils, assuming it doesn't slow down performance significantly. Besides, half of the dojo code base is there to work around browser bugs, so this will hardly be unprecedented. Comment the reference to the eclipse bug though.

comment:12 Changed 13 years ago by Adam Peller

Resolution: fixed
Status: newclosed

comment:13 Changed 13 years ago by dylan

Milestone: 0.60.4

changing milestone for which this was fixed.

comment:14 Changed 12 years ago by (none)

Milestone: 0.4

Milestone 0.4 deleted

Note: See TracTickets for help on using tickets.