SIMILE javascript timeline won't load in FF. Will load in IE. Error occurs reading "caught exception: TypeError: xml has no properties"

RESOLVED INCOMPLETE

Status

()

RESOLVED INCOMPLETE
11 years ago
8 years ago

People

(Reporter: abo46n2, Unassigned)

Tracking

2.0 Branch
x86
Windows Vista
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

(Whiteboard: [CLOSEME 2010-07-30], URL)

(Reporter)

Description

11 years ago
User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.8.1.10) Gecko/20071115 Firefox/2.0.0.10
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.8.1.10) Gecko/20071115 Firefox/2.0.0.10

"caught exception: TypeError: xml has no properties" occurs every time I load my website that has the SIMILE javascript timeline on it.  The other javascript applications work on the page.  Everything works fine when I open the URL in Internet Explorer.

Reproducible: Always

Steps to Reproduce:
1. Go to URL
2. See Error
3. Get frustrated
Actual Results:  
"caught exception: TypeError: xml has no properties" pops up

Expected Results:  
Shown a timeline with numerous plotted points.  Open in Internet Explorer to see what it should look like.

Comment 1

11 years ago
Just a guess at what the problem might be...

http://abo46n2.googlepages.com/timeline.htm contains the script:

  Timeline.loadXML("anthro.xml", function(xml, url) { eventSource.loadXML(xml, url); });

the server sends http://abo46n2.googlepages.com/anthro.xml with
Content-Type: application/octet-stream


the script at http://simile.mit.edu/timeline/api/bundle.js
makes uses "responseXML" a lot, for example:

var xml=xmlhttp.responseXML;
if(!xml.documentElement&&xmlhttp.responseStream){

I'm guesing 'xml' will be null there since the MIME-type says it's not XML.

Comment 2

11 years ago
Is bug 405790 the same problem? (same error message)
(Reporter)

Comment 3

11 years ago
So does anyone know how to solve this problem?  Everyone coming to my site with Firefox is turning away immediately.  

Comment 4

11 years ago
Configure your web server to serve files ending in .xml as text/xml might help.
(Reporter)

Comment 5

11 years ago
Considering I am using Google page creator and accessibility is limited, is that the only way to solve this problem?  

Comment 6

11 years ago
I really think you should ask the admins of googlepages.com to configure
the server to send .xml files as text/xml by default.
And also provide some means for the site owner (you) to set the media
type on file by file basis.  By sending .xml as application/octet-stream
they are promoting browsers that are sloppy in their handling of
media types (read IE), which can hardly be their intent.

Meanwhile, you could try using overrideMimeType() on the request object:
http://developer.mozilla.org/en/docs/XMLHttpRequest

Given that most of the script files are also external (simile.mit.edu)
the only place I see a possibility of doing that is this line:
  Timeline.loadXML("anthro.xml", function(xml, url) { eventSource.loadXML(xml, url); });

try overriding it on Timeline and perhaps also eventSource.

Note that I'm only guessing here - I could be wrong about what the problem
is in the first place...
This bug was originally reported on Firefox 2.x or older, which is no longer supported and will not be receiving any more updates. I strongly suggest that you update to Firefox 3.6.6 or later, update your plugins (flash, adobe, etc.), and retest in a new profile. If you still see the issue with the updated Firefox, please post here. Otherwise, please close as RESOLVED > WORKSFORME
http://www.mozilla.com
http://support.mozilla.com/kb/Managing+profiles
http://support.mozilla.com/kb/Safe+mode
Whiteboard: [CLOSEME 2010-07-30]
Version: unspecified → 2.0 Branch
No reply, INCOMPLETE. Please retest with Firefox 3.6.8 or later and a new profile (http://support.mozilla.com/kb/Managing+profiles). If you continue to see this issue with the newest firefox and a new profile, then please comment on this bug.
Status: UNCONFIRMED → RESOLVED
Last Resolved: 8 years ago
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.