[whatwg] Quirks mode handling of rowspan="0"
bzbarsky at MIT.EDU
Mon Sep 3 06:28:44 PDT 2012
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.
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.
More information about the whatwg