Scriptacolous unusable on Firefox 3 with XHTML 1.1 document
Reported by Urd | August 1st, 2008 @ 06:31 PM
I am trying to get lightbox to work on an XHTML 1.1 conform document, but it isn't working because Firefox 3 refuses to load scriptaculous.
In the error console I find two errors. 1 refering directly to scriptaculous, the other being a result of scriptaculous not loading.
The errors are:
Error: uncaught exception: [Exception... "Operation is not supported" code: "9" nsresult: "0x80530009 (NS_ERROR_DOM_NOT_SUPPORTED_ERR)" location: "http://js/scriptaculous.js Line: 30"]
and
Error: Builder is not defined
Source: http:///js/lightbox.js
Line: 132
I'm using the latest versions available of Prototype, scriptaculous and lightbox.
Comments and changes to this ticket
-
Thomas Fuchs November 20th, 2008 @ 04:54 PM
- → State changed from “new” to “invalid”
We're not supporting XHTML 1.1 when served as XML, although I'd would welcome a patch that makes things work (if the patch isn't too invasive). Try serving as text/html.
-
Thomas Fuchs November 20th, 2008 @ 05:08 PM
- → State changed from “invalid” to “resolved”
Actually I just pushed a patch that (possibly) fixes this, please see #95.
Please Login or create a free account to add a new comment.
You can update this ticket by sending an email to from your email client. (help)
Create your profile
Help contribute to this project by taking a few moments to create your personal profile. Create your profile »
script.aculo.us is an open-source JavaScript framework for visual effects and interface behaviours.
Source available from github
The Git repository resides at:
http://github.com/madrobby/scriptaculous
Check out the current development trunk with:
git clone git://github.com/madrobby/scriptaculous.git
As script.aculo.us 1.xx is feature-frozen, this development trunk is for bugfixes only.
New development should happen only for
script.aculo.us 2.
Creating a bug report
When creating a bug report, be sure to include as much relevant information as possible. Post a an example that shows off the problem. Preferably, alter the unit tests and show through either changed or added tests how the expected behavior is not occuring.
