On Thu, May 15, 2008 at 6:37 AM, RobG <[EMAIL PROTECTED]> wrote: > User agents should ignore unrecognised attributes, but as the OP > discovered, their use can create problems in other ways.
Yes, that is a big risk. I meant to mention that in my last reply. If you are aware of these risks when you are creating your custom attributes, you are much more likely to create attribute names that will likely never conflict with some browser custom attribute or built-in method on a DOM element. For the OP, 'attr' is clearly a bad choice, but all I would suggest is prefix/suffix like 'foo_attr' as opposed to just not using them altogether. -justin --~--~---------~--~----~------------~-------~--~----~ 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 rubyonrails-spinoffs@googlegroups.com 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 -~----------~----~----~----~------~----~------~--~---
