|
|
Hi Amber, the error was exactly the trailing comma. Now it's loading but I've got other errors. thank you very much anyways. I'm going to try the newest version of amber and maybe this solves the problems. Kind regards, Paul Am Donnerstag, 29. März 2012 15:09:39 UTC+2 schrieb Amber Milan Eskridge: I strongly suspect the error to be in this call, but I do not spot it. I came to this page:
and suspect it could be this error but am not sure. Maybe removing the last comma in the array helps. On Thu, Mar 29, 2012 at 10:13 AM, paul <[hidden email]> wrote:
Hi Amber,
sure. And thank you already for giving me a hint.
amber.load({ files: ['../../flow/js/Flow-Errors.js', '../../flow/js/Flow-Announcements.js', '../../flow/js/Flow-Models.js', '../../flow/js/Flow-Presenters.js', '../../kando/js/KandoUI-Errors.js', '../../kando/js/KandoUI-Models.js', '../../kando/js/KandoUI-Announcements.js', '../../kando/js/KandoUI-Presenters.js', ],
ready: function (){window.kando = smalltalk.KandoUI._open()}})
Do you think it's the error is just in there or in one of the files?
Kind regards,
Paul
Am Donnerstag, 29. März 2012 02:05:17 UTC+2 schrieb Amber Milan Eskridge:
That line in amber.js depends on what you give as arguments to the loadAmber-Function. Can you show the loadAmber-call of your code?
On Wed, Mar 28, 2012 at 2:22 PM, paul <[hidden email]> wrote:
Hi Nicolas,
we have an javascript error in IE7 and 8. Do you have encountered something like that before? what could be the problem with the split?
SCRIPT5007: no value for attribute "split" Object is Null or undefinied
amber.js, row 111 character 4
Thank you for your help.
Kind regards,
Paul
Am Mittwoch, 31. August 2011 12:10:31 UTC+2 schrieb laurent:
raaaahhhh IE testing
In IE7 & 8 it's not possible to call appendChild on SCRIPT node.
To make this work, I've changed:
TagBrush>>appendChild: anElement
"In IE7 and IE8 appendChild fails on several node types. So we need to check" < var element=self['@element']; if (null == element.canHaveChildren || element.canHaveChildren) {
element.appendChild(anElement); } else { element.text = anElement.innerHTML;
} >
Looks ugly and hacky. Is there a way to handle cross-browser compatibility better ?
Laurent
Am Mittwoch, 31. August 2011 12:10:31 UTC+2 schrieb laurent:raaaahhhh IE testing
In IE7 & 8 it's not possible to call appendChild on SCRIPT node.
To make this work, I've changed:
TagBrush>>appendChild: anElement
"In IE7 and IE8 appendChild fails on several node types. So we need to check" < var element=self['@element']; if (null == element.canHaveChildren || element.canHaveChildren) {
element.appendChild(anElement); } else { element.text = anElement.innerHTML;
} >
Looks ugly and hacky. Is there a way to handle cross-browser compatibility better ?
Laurent
Am Mittwoch, 31. August 2011 12:10:31 UTC+2 schrieb laurent:raaaahhhh IE testing
In IE7 & 8 it's not possible to call appendChild on SCRIPT node.
To make this work, I've changed:
TagBrush>>appendChild: anElement
"In IE7 and IE8 appendChild fails on several node types. So we need to check" < var element=self['@element']; if (null == element.canHaveChildren || element.canHaveChildren) {
element.appendChild(anElement); } else { element.text = anElement.innerHTML;
} >
Looks ugly and hacky. Is there a way to handle cross-browser compatibility better ?
Laurent
|
Locked
