That is, the elements hear ordinary letters, numbers, clicks, and deletions but not things like Home, End, or the arrow keys. So the elements still work but minimally.
In ALL things, strive for ><>, Chris On Sat, Feb 13, 2010 at 10:38 PM, Chris <[email protected]> wrote: > That happens when I hack into a gadget and add some UI, so I assume that > the keyboard listeners are added when the page loads. So if your gadget's > JavaScript modifies the UI, you might need to manually add some listeners. > Or maybe there's a built-in function you can call to add listeners onto all > new page elements. > > In ALL things, strive for ><>, > Chris > > > > On Sat, Feb 13, 2010 at 6:31 PM, Jeff Richley <[email protected]>wrote: > >> Have you encountered not being able to click buttons and edit text >> fields in your gadget? When I look in the log I see events such as >> "Prevent default: : [object KeyboardEvent]". From time to time I am >> able to interact with the gadget and then it is back to non- >> interactable. I'm sure this is something I am doing, can anyone shed >> light on this for me pretty please. I'm guessing it is me not using >> wave properly. >> >> -- >> You received this message because you are subscribed to the Google Groups >> "Google Wave API" group. >> To post to this group, send email to [email protected]. >> To unsubscribe from this group, send email to >> [email protected]<google-wave-api%[email protected]> >> . >> For more options, visit this group at >> http://groups.google.com/group/google-wave-api?hl=en. >> >> > -- You received this message because you are subscribed to the Google Groups "Google Wave API" 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/google-wave-api?hl=en.
