I have done as described above, see below. But, it does not fix the bug. We don't use Silva, but plone on zope297 with Kupu 1.3.9, zope297. But, yes, there is no bug when I use seamonkey, but firefox.
I would be happy if any of you had suggestions to how I should fix the bug.
Flemming
.../Products/kupu/common/sarissa.js
else{ /* end IE initialization, try to deal with real browsers now ;-) */
if(_SARISSA_HAS_DOM_CREATE_DOCUMENT){ if(window.XMLDocument){
/**
* <p>Emulate IE's onreadystatechange attribute</p>
*/ XMLDocument.prototype.onreadystatechange = null;
/**
* <p>Emulates IE's readyState property, which always gives an integer from 0 to 4:</p>
* <ul><li>1 == LOADING,</li>
* <li>2 == LOADED,</li>
* <li>3 == INTERACTIVE,</li>
* <li>4 == COMPLETED</li></ul>
* FB has outcommented the following line:
* XMLDocument.prototype.readyState = 0;
*/
/**
* <p>Emulate IE's parseError attribute</p>
*/
I have done as described above, see below. But, it does not fix the bug. We don't use Silva, but plone on zope297 with Kupu 1.3.9, zope297. But, yes, there is no bug when I use seamonkey, but firefox.
I would be happy if any of you had suggestions to how I should fix the bug.
Flemming
.../Products/ kupu/common/ sarissa. js
else{ /* end IE initialization, try to deal with real browsers now ;-) */ SARISSA_ HAS_DOM_ CREATE_ DOCUMENT) {
if(window. XMLDocument) {
XMLDocumen t.prototype. onreadystatecha nge = null; prototype. readyState = 0;
if(_
/**
* <p>Emulate IE's onreadystatechange attribute</p>
*/
/**
* <p>Emulates IE's readyState property, which always gives an integer from 0 to 4:</p>
* <ul><li>1 == LOADING,</li>
* <li>2 == LOADED,</li>
* <li>3 == INTERACTIVE,</li>
* <li>4 == COMPLETED</li></ul>
* FB has outcommented the following line:
* XMLDocument.
*/
/**
* <p>Emulate IE's parseError attribute</p>
*/