Hi Yanosz, Can you provide a couple of concrete examples of silent failures? Maybe post a minimalist page demonstrating a couple of them to Pastie[1]? For the most part (IMHO) silent failures are a Bad Thing and so examples should be reported as bugs. But it doesn't hurt to discuss them first, not least to be sure that you're actually seeing what you think you're seeing (and that it's not a browser bug as opposed to a Prototype bug). :-)
[1] http://pastie.org Thanks, -- T.J. Crowder tj / crowder software / com On Sep 25, 10:53 pm, Jan Luehr <[EMAIL PROTECTED]> wrote: > Hello, > > I'm using prototype & scriptaculous in various Ruby-on-Rails applications, > some of them do a lot of prototype & ajax stuff with RoR-Helpers. > But what I'ven't figured out yet is: > Is there a way to do exception-Handling with prototype? > While classic JavaScript exception handling uses try/catch blocks to handle > exceptions or (if none is available) throw them to browsers. I've discovered > a lot of situations were prototype code fails silently (espacially in IE6) - > making code hard to debug / allowing hardly any debugging at all. > Are there any ways / best-practices for prototype exception-Handling or Script > debugging? > > Thanks, > Keep smiling > yanosz --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Prototype & script.aculo.us" 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/prototype-scriptaculous?hl=en -~----------~----~----~----~------~----~------~--~---
