On Mon, Jan 16, 2006 at 11:50:26AM -0800, Bill Moseley wrote:
> There's other odd things happening. When I first load the page
> clicking on the <a> links nothing happens, and I have to first click
> either on the <th> area or on some link on the page ( like the ajax
> updater for "page next", for example).
Well duh!, as they say.
I've got an inline onclick handler on the <a> tag and I also have
Behaviour setup to add an onclick handler to those <a> tags -- which
replaces the inline ones.
I suppose I could (should) assign unique ids to every link where I
need Ajax.Updater and use behaviour to do both the Event.stop and the
Ajax.Updater for each id -- just to get the javascript out of the
html.
BTW, seems like doing:
Ajax.Updater(); Event.stop(e); return false;
actually somehow returns true because the browser is making both the ajax and
non-ajax request.
Where just:
Ajax.Updater(); return false;
works ok (and when I don't have onclick on the <tr> ).
Maybe I need to learn more about event order to understand why this
isn't working.
--
Bill Moseley
[EMAIL PROTECTED]
_______________________________________________
Rails-spinoffs mailing list
[email protected]
http://lists.rubyonrails.org/mailman/listinfo/rails-spinoffs
