RE: Using DOM to replace media attribute in the link tag on page load

Patrick Garies:

| The first criterion is effectively saying “never”;

So long as there's no functional compliance issue, that may be so. At the moment, I know of no spec I need to validate against that requires the new mime types.

| I’m not quite sure what you mean by “partially” or “doesn't address 
| current conditions”. If, by those, your message is that something 
| shouldn’t be used until it can be freely used in all commonly used 
| browsers (i.e., “doesn't address current conditions”) and that 
| workarounds (i.e., “partial” adherence to RFC4329 due to the IE 
| workaround) mean that a solution shouldn’t be used, I simply have to 
| disagree.

I have no qualms about conditionally using something that has a visual or functional effect, but I see no purpose in conditionally providing two different content descriptions when one will suffice.

Obsoleting of text/javascript does not imply we must immediately change all our web pages. Text/javascript wasn't registered until RFC4329, and yet its prior use did not contravene any standard. Now it's registered only to be obsoleted, but I see nothing in the RFC to indicate that use of an obsolete mime type makes a web page non-compliant.

David Perrell

Received on Tuesday, 29 July 2008 02:13:10 UTC