Oh.. and keyboard events are almost always in the document scope (form elements are one of the few exceptions), so that would be the best option I guess.
On Dec 31, 3:56 pm, Wizz <[EMAIL PROTECTED]> wrote: > Linking an event to every cell is a possibility, but extremely slow > when you have more then 100 cells (or something like that). > > Best way is to attach your events to the table element and work from > there... You can use the prototype event object to see which element > was clicked and so on... > > On Dec 31, 11:26 am, "Antonio CS" <[EMAIL PROTECTED]> wrote: > > > You want to have a table able to edit it's own cells? I think scriptaculus > > as something like this or will have! > > But I think what you can do is just go through every td in the table and > > link to an event > > > On Dec 31, 2007 9:35 AM, bartocc <[EMAIL PROTECTED]> wrote: > > > > Hi, > > > > I there an easy way to have a table observe keyboards events > > > (keyup, ...) ? > > > > So far, the only hack I could find was to observe these events on the > > > document, and then forward them to the table ... > > > > Thx for the help --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
