Just to add my two cents, the body approach works well as long as you work with classes, not a single id, not with the id. Something like action_youractionname and controller_yourcontrollername. Modernizr has a similar approach to specify what features are available.
On Tue, Jun 28, 2011 at 8:29 AM, Chris Braddock <[email protected]>wrote: > Thanks. The 2nd option you're suggesting (body IDs) is what I originally > had in mind until this debate broke out against using the ID attribute on > the body tag <http://dailyjs.com/2010/04/27/unobtrusive-js/> (which I kind > of ended up liking). > > But, for the sake of pragmatism, I might have to again revisit my approach > thanks to this new twist. > > > -- > You received this message because you are subscribed to the Google Groups > "Ruby on Rails: Talk" group. > To view this discussion on the web visit > https://groups.google.com/d/msg/rubyonrails-talk/-/u6YFgqb4qXgJ. > > 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-talk?hl=en. > -- You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" 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-talk?hl=en.
