Two unrelated comments.<div><br></div><div>First, it seems a bit odd to me that <input type=email> and <input type=url> are validated (for typeMismatch problems) but <input type=tel> isn't. I know it's prohibitively difficult to perfectly validate telephone number formats given the variety around the world, but it's also prohibitively difficult to validate email addresses per the relevant RFC, which is why HTML5 specs a much simpler algorithm that at least rejects obviously bad input.</div>
<div><br></div><div>It seems like perhaps <input type=tel> could set typeMismatch if the input contained no numeric digits at all, or maybe if it contained characters outside 0-9, +, -, (, ), ' ', ...? Maybe the level of "validation" provided by these proposals is so low that it's not worth doing, though.</div>
<div><br></div><div>Second comment: There are 4 instances of a small typo in attribute lists, where "..., required, size, ..." is rendered as "..., required size, ...". See the "bookkeeping details" portions of sections 4.10.4.1.19, 4.10.4.1.20, 4.10.4.1.21, and 4.10.4.1.22.</div>
<div><br></div><div>PK</div>