That is a very strong statement, Tobie. Overly. Thank you very much. ) I'd rather you break it down to parts. Like, "that particular snippet of yours.." or somethin'. 'Cos "I've eaten a god on Prototype" (how they say it in our lands) by now. I understand you're in the Prototype team and all. And the rest of the world knows much less about this child than you do.. ) But.. I, too, regularly study all changes even to minor versions and have created a Prototype reference cheatsheet for colleagues way before it was available on the web.
Now, what I understand about "F.SpecificElementExtensions", it doesn't necessarily return the right value when it should. That's the fact. I've given you an example. Perhaps, some FF plugins were preventing it from working the right way. Then, second question, what I understand about $$(), it returns a plain array with unextended elements (if IE is used, for instance). Is it by design? Thanks. Best regards, Andrew Revinsky On Jul 24, 9:22 pm, Tobie Langel <[EMAIL PROTECTED]> wrote: > Hi Andrew, > > You're misunderstanding a lot of different things here. > > I suggest you read the article "How Prototype Extends the > DOM":http://prototypejs.org/learn/extensions > > Hope that helps. > > Regards, > > Tobie > > On Jul 24, 8:39 am, Andrew Red <[EMAIL PROTECTED]> wrote: > > > > > Tobie, hello! > > > I use FF 2.0.x.x with Firebug on Win XP RU. I'm not sure if the latter > > part matters, anyhow. > > > Just after I've upgraded to 1.5.1.1, all calls to $() function were as > > if I just did document.getEl..tById(), not extended. And it was so > > only in FireFox. However, in IE elements were extended fully. > > > So I noticed FireBug was giving me errors like ".up() method is null > > or undefined" and ".addClassName method is null or undefined" (and > > such). > > > Tracing back the callstack I figured, the Element.extend method was to > > blame. There's an "if" statement (the second line): > > > if (!element || !element.tagName || element.nodeType == 3 || > > element._extended || F.SpecificElementExtensions || element == > > window) ... > > > And in my FF, F.SpecificElementExtensions always resolved to true, > > while in IE - false. So, in FF, the element was returned back, having > > no extended methods whatsoever. Really upset me. > > > I first checked your blog, then went here. Just to find that mild > > solution to my problem by eliminating those niceties. I believe, this > > describes my problems. > > > Oh, by the way, is the $$() function supposed to return unextended > > elements? > > > Like, I happen to use $() so that this snippet would work (3rd line): > > > $$('.menuBar a').each(function(el) { > > if (!window.location.href.endsWith(el.href)) return; > > > > $(el).addClassName('selected').up(0).addClassName('selected'); > > throw $break; > > }); > > > Thanks! > > > Best regards, > > > Andrew Revinsky > > > On Jul 18, 7:17 pm, Tobie Langel <[EMAIL PROTECTED]> wrote: > > > > Hi Andrew, > > > > Could you be a it more specific and / or open a ticket for the missing > > > methods, as this issue is unheard of as far as I know. > > > > If this is true it is definitely a bug and needs to be dealt with. > > > > Thanks and best regards, > > > > Tobie > > > > > I became aware of SpecificElementExtensions only because my FF 2.0.xxx > > > > started blurting out errors with Prototype v 1.5.1.1 that certain > > > > functions on extended DOM elements ( $(..) ) don't actually exist.- > > > > Hide quoted text - > > > > - Show quoted text -- Hide quoted text - > > - Show quoted text - --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Spinoffs" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/rubyonrails-spinoffs?hl=en -~----------~----~----~----~------~----~------~--~---
