On 13 Sep 2007, at 01:15, Michael Koziarski wrote: > Browsers understand <br /> just fine, I'm suggesting we be pragmatic.
Actually browsers don't understand <br /> - it's their lax error handling that makes it work. Most XHTML pages would actually fail if run through an XML parser as they are ill-formed. Take Basecamp's homepage page for example - there's a meta tag without the /> at the end which makes it ill-formed. It's the fact that they're served as text/html that makes them work. > What's the real problem we're trying to solve? What's the impact > of not solving it? Well in my case I'm trying produce valid HTML4 that will pass WCAG without warnings to appease my local government / lottery funded clients who require accessible websites. > What's the problem with installing a plugin which does this? I have no problem, but I personally feel that Rails should be able to generate valid markup out of the box. Anyway I've closed the ticket with a link to the available plugin. Andrew White --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
