W3C home > Mailing lists > Public > www-html-editor@w3.org > July to September 2006

[xhtml2] ContentTypes data type

From: <karl@w3.org>
Date: Thu, 17 Aug 2006 03:27:44 -0000
To: www-html-editor@w3.org
Message-Id: <20060817032750.E00C04F5B8@homer.w3.org>

Hi,
This is a QA Review comment for "XHTML 2.0"
http://www.w3.org/TR/2006/WD-xhtml2-20060726/
2006-07-26
8th WD

About http://www.w3.org/TR/2006/WD-xhtml2-20060726/abstraction.html#s_common_attrtypes

The specification says:

	"The user agent must combine this list with its own 
	list of acceptable media types by taking the 
	intersection, and then use the resulting list as the 
	field value of the accept request header when 
	requesting the resource using HTTP."

This will lead to difficult corner cases, which means a lot of test cases. 
	1. HTTP has precedence as defined in specifications.
	2. How to resolve content/types preference with different q values
	
	"A user agent must imitate similar behavior when using 
	other methods than HTTP."
	
What is *imitate* in this context? 

	"For instance, when accessing files in a local filestore, 
	<p src="logo" srctype="image/png, image/jpeg"> might cause 
	the user agent first to look for a file logo.png, and then 
	for logo.jpg."
	
Do you mean an application which will handle a "file://" for example? Many browsers interpret the content of these files depending of their extensions if given.
In case of conflicts, what MUST be the behaviour of the user agent?
	
	<p src="logo.svg" srctype="image/png, image/jpeg">




-- 
Karl Dubost - http://www.w3.org/People/karl/
W3C Conformance Manager, QA Activity Lead
   QA Weblog - http://www.w3.org/QA/
      *** Be Strict To Be Cool ***
Received on Thursday, 17 August 2006 03:28:22 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 27 March 2012 18:17:55 GMT