Naw, don't worry about it Alex, it's just that I think that same question and answer has been posted about 10 times in about as many days
On Nov 8, 2007 2:14 PM, Alex MacCaw <[EMAIL PROTECTED]> wrote: > (hangs head in shame) > > Thanks for the quick responses > Alex > > On Nov 8, 2007 6:56 PM, Tom Gregory <[EMAIL PROTECTED]> wrote: > > > > > Amen, and amen. It's (un)common courtesy to read a FAQ and spend a > > couple of minutes with Uncle Google before posting. People are > > forgetting that. > > > > I don't see an official FAQ at prototypejs.org. > > http://www.google.com/search?q=FAQ+site%3Aprototypejs.org > > > > I know a couple of users have worked on one--I think it'd be useful > > to have an official one. > > > > > > TAG > > > > On Nov 8, 2007, at 11:43 AM, Matt Foster wrote: > > > > > > > > Right? The same questions just keep coming up, it'd be sweet if people > > > > > searched before they posted. This is a pretty apparent complication > > > of prototype, as well as thoroughly documented. > > > > > > Quoted from http://prototypejs.org/learn/extensions > > > > > > "Because the prototype of the native browser object is extended, all > > > DOM elements have Prototype extension methods built-in. This, however, > > > isn't true for IE which doesn't let anyone touch > > > HTMLElement.prototype. To make the previous example work in IE you > > > would have to extend the element with Element.extend(). Don't worry, > > > the method is smart enough not to extend an element more than once." > > > > > > > > > On Nov 8, 12:32 pm, "Brian Williams" <[EMAIL PROTECTED]> wrote: > > >> You know Tom, you should really just make that part of your sig- > > >> line... > > >> > > >> then you wouldn't have to type it out as much... > > >> > > >> just a thought lol > > >> > > >> On Nov 8, 2007 12:22 PM, Tom Gregory < [EMAIL PROTECTED]> wrote: > > >> > > >> > > >> > > >>> Yup. > > >> > > >>> IE doesn't extend *all* elements the way other browsers do, so > > >>> you'll > > >>> have to make sure it happens. Passing the element through $() takes > > > > >>> care of this, as Prototype makes sure the element is properly > > >>> extended as part of the function. > > >> > > >>> TAG > > >> > > >>> On Nov 8, 2007, at 10:04 AM, Alex MacCaw wrote: > > >> > > >>>> We're getting an issue with the latest prototype, IE6 and the > > >>>> function > > >>>> addClassName. The error doesn't occur in any other browsers. > > >>>> When we call addClassName on an element, IE displays an error 'A > > >>>> Runtime Error has occured.' The error msg is: 'Object doesn't > > >>>> support > > >>>> this property or method'. One more thing to add; we're calling this > > >>>> function on an element we've created via document.createElement. > > >>>> If we > > >>>> call it on an element created with the new Element syntax, it > > >>>> works. I > > >>>> presume 'new Element' adds extra functions onto the element? > > > > > > > > > > > > > > > > http://www.eribium.org | <http://juggernaut.rubyforge.org> > > http://juggernaut.rubyforge.org | <http://www.aireofs.com> > > http://www.aireofs.com | Skype: oldmanorhouse > > > > > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
