Topic: Bug In Opera (Page 1 of 1)

My page htpp://redsplat.org/ doesn't work in Opera (it works in both Chrome and FF). As far as I can figure out it is because it runs both my fadeIn and fadeOut function on the same time.

Anybody knows how to fix this?

First of all, did you check the error console ( Tools > Avanced > Error Console ) ? Even better, did you enable the "stack trace" as mentioned " stacktrace: n/a; see opera:config#UserPrefs|Exceptions Have Stacktrace " in the error console to see exactly what and where the error is ?

When doing so, Opera reports the following recurring error:

JavaScript - http://redsplat.org/
Unknown thread
Error:
name: TypeError
message: Statement on line 57: Cannot convert undefined or null to Object
stacktrace:   Line 57 of linked script http://redsplat.org/script.js
                document.title='redsplat - '+document.getElementById('title').innerHTML;
  ...

Which is fair considering that your page is invalid and you put an XML declaration right in the middle of the document.

quote:

---

Line 20, Column 9: XML Parsing Error: XML declaration allowed only at the start of the document
<?xml version="1.0" encoding="ISO-8859-1"?><h1 id="title">Weblog</h1><p>In t...

source: W3C validator on http://redsplat.org/

---

I know,street HTML and all, but I have no idea how user agents are supposed to treat such markup. It's already rare to see the same behavior across browsers with valid markup, one can't possibly expect invalid markup to be treated any better.

Seeing from the other threads about your site and what I saw in the source code of your pages and scripts, it seems that you're a little bit confused about this web thing and try various things without really understanding or knowing what you are doing. I know it's not sexy but you should try to get the basics right before jumping onto more advanced things : read a bit about valid HTML and semantic markup ( IMO the easy way is HTML5 with XML syntax if you want XML ), DOM ( using innerHTML to inject content end users can contribute to is bad bad and super bad. Using innerHTML instead of textContent ain't very good either, inline events aren't really nice and you look into progressive enhancement : right now you site doesn't work in a browser with JS on but no XHR )

Don't hesitate to ask if you have any specific question.
Hope all this helps a bit.



(Edited by poi on 07-06-2009 01:17)

Note that there is also a CSS error

Invalid value for property: opacity

Line 1:
  1.3877787807814457e-16
  ----------------------^

The line 1, seems wrong in itself but it's a clear indication of something going on in a setTimeout, setInterval or an event handler.