> How would it be easier for a novice to learn that they have to create > a plugin and monkey patch the tag helper method if they need to > produce valid HTML to pass WCAG 1.0 without producing warnings. >
It isn't important enough to most users that they'll be forced to do that. > > Second, by presenting an extra configuration option, you discourage > > people from enhancing that feature, because now they're pressured to > > write two versions. > > Have you looked at the patch? All it does is control the default for > the last parameter to the tag helper method - I'd hardly call it a > feature! I also doubt it'd require writing two versions of anything. > It's a small feature, but it is a feature. More functionality means more to maintain, more tests to break, and more considerations when writing a plugin. > > Third, by giving users the option of creating html4 documents, you are > > lending validity to the idea that html4 is fine. I believe few people > > share that feeling. > > HTML4 is perfectly fine - I don't recall the W3C revoking it at any > point. I'm assuming that you serve your pages as text/html in which > case all you are doing is producing invalid HTML as that's how the > browser will treat it.[1] > HTML4 is fine. But it isn't fine enough that it deserves the support of Rails. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
