[Prototype-core] Bug from prototype?

2007-12-04 Thread [EMAIL PROTECTED]
Hello all, I'm using the prototype.js in my application and i have an error: Error: element has no properties Source File: http://www/application/js/prototype.js Line: 3844 function getEventID(element) { if (element._eventID) return element._eventID; arguments.callee.id = arguments.callee.id

[Prototype-core] Re: Bug from prototype?

2007-12-04 Thread Mislav Marohnić
We don't know if you're doing something wrong because you haven't told or shown us what you are doing. But, the code you are referring to is pretty internal to event handling, so I don't think you might be doing something wrong. What we need from you if full code where this happens (use

[Prototype-core] Re: Bug from prototype?

2007-12-04 Thread Mislav Marohnić
That's a lot of code to dig through. Couldn't you just save the result HTML document from the browser instead of pasting all the sources? We are interested only in JavaScript code and HTML that it applies to. On Dec 4, 2007 3:48 PM, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote: P.S.: (

[Prototype-core] Re: Bug from prototype?

2007-12-04 Thread [EMAIL PROTECTED]
Archive cliente_upd.php : ? include(inc/lib.inc.php); #define de ACAO define(NG_ACAO, CLI_DETAIL); #verifica_permissao checkPermission(); $page = new Smarty(); $cl = new clientes(); $cl-NR_CLIENTE = $_GET[nr]; $cl-load(); if(empty($cl-NOME)) { $page-assign(not_updated, true);

[Prototype-core] Re: Bug from prototype?

2007-12-04 Thread Mislav Marohnić
I took some time to actually read the last bits of the code. First of all, you didn't paste us masks.js, which is pretty important for this case. But, you don't have to because the source of your problems is not Prototype framework, but the fact you are trying to observe events by passing NULL

[Prototype-core] Re: API Request: Function.argumentNames(); Function.methodize();

2007-12-04 Thread John-David Dalton
Thanks for clearing that up. I knew what the first one did but not the second. I was actually stating that the API docs dont have these in it. Could one of the core team add these methods to their documentation. --~--~-~--~~~---~--~~ You received this message

[Prototype-core] Enumerable Map() oddity.

2007-12-04 Thread John-David Dalton
Hi guys, This is really not a bug but I thought I would bring it to your attention. $$('[type=radio]').map(function(el){return el.next()}); // = [label, label] $$('[type=radio]').map(Element.next); // = [label, undefined] The map method is passing 2 params to the iterator. This makes the

[Prototype-core] Re: Bug from prototype?

2007-12-04 Thread Thomas Fuchs
1) Get the current versio of Prototype. You're not using 1.6.0 final. 2) The below means you're trying to observe an event on a non-existing element (your setupOneElementMask function calls observe on null. Please direct usage questions to the rails-spinoffs google group. This group is for

[Prototype-core] Re: Enumerable Map() oddity.

2007-12-04 Thread Jeff Watkins
On 4 Dec, 2007, at 8:23 AM, John-David Dalton wrote: The map method is passing 2 params to the iterator. This makes the Element.next() go nuts cause its second param is used for sibling offset. In PHP array_map only passes the value and not the index. It makes since for Enumerable.each()

[Prototype-core] Re: Enumerable Map() oddity.

2007-12-04 Thread Sam Stephenson
Hi John- On Dec 4, 2007, at 10:23 AM, John-David Dalton wrote: $$('[type=radio]').map(function(el){return el.next()}); // = [label, label] $$('[type=radio]').map(Element.next); // = [label, undefined] You can use Enumerable#invoke instead of map: $$([type=radio]).invoke(next) // = [label,

[Prototype-core] Re: Enumerable Map() oddity.

2007-12-04 Thread John-David Dalton
Thanks Sam ! :) --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Prototype: Core group. To post to this group, send email to prototype-core@googlegroups.com To unsubscribe from this group, send email to [EMAIL

[Prototype-core] Re: Enumerable Map() oddity.

2007-12-04 Thread Mislav Marohnić
On Dec 4, 2007 6:19 PM, John-David Dalton [EMAIL PROTECTED] wrote: Thanks Sam ! :) The selector I posted is, IMO, better and faster solution. But it's true, I totally forgot about how invoke fits perfectly here. --~--~-~--~~~---~--~~ You received this message