> Should be fixed here (i think).  Otherwise you can fork the rep and  
> make your own fixed copy, thats what im about to do now.

> Jose

> On Apr 18, 2008, at 3:26 PM, MZBPhotoartl...@gmail.com wrote:

> > Why hasn't the trunk been updated yet. It's been a month and I'm
> > getting irritated fixing this problem for each app. Do we need to
> > submit a bug report to the project leaders?

> > On Apr 8, 5:47 pm, broox <derek.br...@gmail.com> wrote:
> >> You rule.  Good find.

> >> On Mar 25, 8:53 am, AkitaOnRails <fabioak...@gmail.com> wrote:

> >>> Ok, I figured out the problem.

> >>> On active_scaffold.js (make sure you're looking at the copy on your
> >>> public/javascript folder), around line #266 there is this code:

> >>> this.adapter.getElementsByClassName('cancel').each(function(elem) {

> >>> The guys at caboose (http://blog.caboo.se/articles/2008/3/21/safari-3-1-breaks-your-app
> >>> ) figured out that bothSafariand Firefox
> >>> implements a new getElementsByClassName() function that breaks
> >>> compatibility. The solution (there are variants) is this:

> >>>     this.adapter.select('.cancel').each(function(elem) {

> >>> In this case I am replacing with Prototype's select() mechanism.  
> >>> This
> >>> worked for me onSafari3.1.

> >>> On Mar 24, 9:13 pm, David Richardson  
> >>> <david.richard...@channel200.net>
> >>> wrote:

> >>>> I'm having a tough time seeing whats going on with '.link'. Anyone
> >>>> else?
> >>>> It's a problem in update.rjstoo. Are 'cancel' links used anywhere
> >>>> else?

> >>>> This is somewhat important.Safari3.1 is out and Firefox 3 is weeks
> >>>> away.

> >>>> david