Re: typesmustmatch xhtml

2014-11-11 0:45, Alice Wonder wrote:

> When the object tag has the typesemustmatch attribute, the W3C validator
> states that it is not allowed in xhtml at this point.

This is a longstanding bug (first reported in 2011): the typemustmatch 
attribute (this is the correct spelling) has not been added to the 
allowed attributes for <object>:
http://bugzilla.validator.nu/show_bug.cgi?id=843
(The HTML5 side of the W3C Validator is based on the validator.nu code, 
and this bug in the W3C Validator simply reflects a bug in the base code.)

> This is why that attribute is important to me, and why I would like it
> to be part of html5 even when sent as XML

It is. The real problem with this attribute is browser support. According to
https://developer.mozilla.org/en-US/docs/Web/HTML/Element/object
only Firefox 27+ is known to support it. However, since the attribute is 
in the HTML5 specification that was recently approved as a W3C 
Recommendation, there is apparently at least one other implementation. 
But apparently the attribute is not widely supported yet; as it is 
expected to just provide some security, it can be used, but cannot be 
relied on.

> So I really want that attribute to be legal in html5 - even when I send
> as XML which is what I prefer to do.

It is. The validator just has an issue. And it has it even when sending 
as text/html; the error message is then “Attribute typemustmatch not 
allowed on element object at this point.” (The part “at this point” was 
once meant to be helpful in some contexts, and I might have been the 
person who suggested it, but I’m afraid it is misleading more often than 
helpful. Here it seems to be saying that the placement or context is 
wrong; but the issue is really that the validator does not recognize 
this attribute at all.)

Yucca

Received on Tuesday, 11 November 2014 05:56:41 UTC