| |||||||||||||
Authors don't code to spec, so browsers and specs need to consider thatAuthors don't code to spec, so browsers and specs need to consider thatPosted Jul 31, 2012 15:39 UTC (Tue) by nickbp (subscriber, #63605)In reply to: Authors don't code to spec, so browsers and specs need to consider that by Velmont Parent article: WHATWG severs collaboration with W3C on HTML
So, I think a strong "boil the ocean and break everything" specification that you mention would actually solve the "web authors don't follow the spec" problem that you mention.
If bad behavior is such a problem, then perhaps the next HTML specs and implementations shouldn't be so permissive of it. Likewise, it should be easy for both the web developer and browser developer to test and verify good behavior. Otherwise the problem will just continue to get worse as more features are piled on.
(Log in to post comments)
|
|||||||||||||