- From: Boris Zbarsky <bzbarsky@MIT.EDU>
- Date: Mon, 03 Sep 2012 09:28:44 -0400
- To: whatwg@lists.whatwg.org
On 9/3/12 2:31 AM, Jukka K. Korpela wrote: > This was the case already in HTML 4.01 Yes, I know. > Generally, attempts at defining "quirks mode" would mean making it an > alternate mode and will not be successful due to the wide variation > across browsers and versions. It's called "quirks" for a reason. See http://dvcs.w3.org/hg/quirks-mode/raw-file/tip/Overview.html The point is to enable new UAs to be written that can actually function on the web. That means specifying quirks mode. > Specifically, as some browsers already support rowspan="0" in quirks > mode, and some don't, you cannot ensure backwards compatibility no > matter how you define it. This is not specific to quirks mode. This happens any time there's lack of interop. It's not a new situation. > but it does not help to change it Yes, it does: once all browsers agree, the barrier to entry for new entrants is lower because they just need to implement the behavior everyone already agrees on. -Boris
Received on Monday, 3 September 2012 13:29:18 UTC