Re:The Current State of HTML5 Forms
by bzbarsky on Tuesday March 22, 2011 @01:29PM
(#2355359)
Well, one reason might be that they care about not having buggy code. You may laugh, but for the standards IE9 claims to implement it does a very good job. Much better than Webkit, in my testing.
> There should really be just one rendering engine.
No. That's really a terrible idea, because different rendering engine consumers have different priorities.
Luckily, even "webkit" has a number of forks that are somewhat incompatible for precisely that reason. So we're in no danger of this "one rendering engine" thing.
(A note: while we've already been close to having one rendering engine with a priority of "change nothing", having one with pretty much any other priority set is no better; those priorities will be wrong for _some_ consumer.)
> There should really be just one rendering engine.
No. That's really a terrible idea, because different rendering engine consumers have different priorities.
Luckily, even "webkit" has a number of forks that are somewhat incompatible for precisely that reason. So we're in no danger of this "one rendering engine" thing.
(A note: while we've already been close to having one rendering engine with a priority of "change nothing", having one with pretty much any other priority set is no better; those priorities will be wrong for _some_ consumer.)