> If browsers had implemented HTML in complete compliance with the spec, > <hr/ and <hr> would be equivalent, and therefore <hr/> would be > equivalent to <hr>>. This is why pages will render fine, but fail > strict validation.
If browsers had been in strict html compliance then we'd be in an entirely different world. Thankfully we're not. As it stands this patch makes literally *no* difference to users of a rails site, and could be trivially overwritten by a plugin for the developers who worry about such things. Does it really need to be another option added to the framework? -- Cheers Koz --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Core" 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-core?hl=en -~----------~----~----~----~------~----~------~--~---
