After searching the rico forum I found this entry:

http://forum.openrico.org/topic/966#1889 (forum seems to be down at the moment, hopefully will be up again soon ;))

That issue seems to be fixed in newer versions. Unfortunately we can't upgrade to a new version of the library right now - so integration of trinidad must be postponed for us.

Thanks for the hints.

Christopher

Adam Winer schrieb:
I'd ask the Rico developers for some advice here.
Slamming Object.prototype means that they're
breaking everyone else's code of the form:

 for (var key in someObject)
   ...

It's certainly a fun way of manipulating JS, but
it's not very friendly towards integrating with
other JS libraries, something I think a lot of
DHTML developers either ignore or just don't
care about.

-- Adam


On 2/21/07, Christopher Cudennec <[EMAIL PROTECTED]> wrote:
I assume you're right. We're using Rico for example which has the
following lines of code:

Object.prototype.extend = function(object) {
    return Object.extend.apply(this, [this, object]);
  }

Is there any way to get around that? I'm afraid we can't hinder other
libraries from using that mechanism, can we?

Christopher

Adam Winer schrieb:
> I'm hypothesizing a JS library that is overriding Object.prototype, for
> example, and making "extend" show up in our object in Firefox.
> That'd be a pretty bad bug in that library...
>
> -- Adam
>
> On 2/19/07, Christopher Cudennec <[EMAIL PROTECTED]> wrote:
>> Yes, a couple of. Do you think about a special one? Is there anything I
>> can search for in these libraries? Although I stopped trying to use
>> trinidad for the moment because I ran into too many problems, I'd
>> definitely like to know where the problem is :)
>>
>> Christopher
>>
>> Adam Winer schrieb:
>> > I'm just baffled trying to imagine how this got there.
>> >
>> > Are you running with any other JS libraries present?
>> >
>> > -- Adam
>> >
>> >
>> > On 2/16/07, Christopher Cudennec <[EMAIL PROTECTED]> wrote:
>> >>
>> >> tempParams['extend'] seems to be a JS function (I used firebug for
>> >> debugging). I haven't figured out how it got there but I don't get
>> this
>> >> error using IE. Anything you need for interpreting the error?
>> >>
>> >> Christopher
>> >>
>> >> Adam Winer schrieb:
>> >> > Oops, I meant what is tempParams['extend']?  Is
>> >> > it a JS function?  If so, how did it get into tempParams?
>> >> >
>> >> > -- Adam
>> >> >
>> >> >
>> >> > On 2/15/07, Adam Winer <[EMAIL PROTECTED]> wrote:
>> >> >> What is tempParams['source'] here?  A DOM node, etc.?
>> >> >>
>> >> >> -- Adam
>> >> >>
>> >> >>
>> >> >> On 2/15/07, Christopher Cudennec <[EMAIL PROTECTED]> wrote:
>> >> >> > Hi... I'm getting closer to integrating trinidad :).
>> >> >> >
>> >> >> > My next problem (also already posted some weeks ago) is a JS
>> error
>> >> >> that
>> >> >> > only occurs in Firefox. IE does not have any problems. I get
>> this
>> >> >> > exception after submitting the very first page of my app (login
>> >> form):
>> >> >> >
>> >> >> > Fehler: uncaught exception: [Exception... "Node was not found"
>> >> code:
>> >> >> > "8" nsresult: "0x80530008 (NS_ERROR_DOM_NOT_FOUND_ERR)"
>> location:
>> >> >> > "http://localhost:8080/op/adf/jsLibs/Common11-m7.js Line: 4106"]
>> >> >> >
>> >> >> > Debugging revealed that tempParams contains to values: "source"
>> >> (the
>> >> >> > login button) and "extend" (a function ?!). Trying to remove the
>> >> >> second
>> >> >> > value causes the exception.
>> >> >> >
>> >> >> > 4103 if(isDOM)
>> >> >> > 4104 {
>> >> >> > 4105 for(var paramName in tempParams)
>> >> >> > 4106 form.removeChild(tempParams[paramName]);
>> >> >> > 4107 }
>> >> >> > 4108 }
>> >> >> >
>> >> >> >
>> >> >> > Sounds familiar or any suggestions?
>> >> >> >
>> >> >> > Christopher
>> >> >> >
>> >> >>
>> >> >
>> >> >
>> >>
>> >>
>> >
>> >
>> ------------------------------------------------------------------------
>> >
>> > No virus found in this incoming message.
>> > Checked by AVG Free Edition.
>> > Version: 7.5.441 / Virus Database: 268.18.3/693 - Release Date:
>> 19.02.2007 17:01
>> >
>>
>>
>
>





Reply via email to