W3C home > Mailing lists > Public > public-diselect-editors@w3.org > July to September 2005


From: Rhys Lewis <rhys.lewis@volantis.com>
Date: Wed, 24 Aug 2005 10:43:07 +0100
Message-ID: <D18551A6C7EA6241B960D4909EB75DF5013AD485@squid.volantis-uk>
To: <chaals@opera.com>
Cc: <public-diselect-editors@w3.org>

Hello Charles,

Once again, thanks for your comments on the content selection last call in 

This mail documents DIWG's response to your comment numbered 2. DIWG has recorded this comment as McCathieNevile-2.

Comment McCathieNevile-2: Minimum Font Size

2. There is no clear way in the spec of finding out the user's font size. Most modern browsers have implemented a minimum font size setting, because users wanted it. Finding out what that is would be extremely helpful for authors, whereas just giving them the pixel size of the screen forces them to make guesses about the font size being used.

DIWG official response

The particular functions described in the document are equivalents of those proposed for CSS Media Queries. We have deliberately retained exactly the same functions as those used in that specification. This was stressed [1] in the document as follows: "They have been chosen to implement features similar to those associated with Media Queries. No attempt as been made to change the Media Queries function, except for two additions in the case of aspect ratio and the addition of a defaulting mechanism." The CSS Media Queries function set does not contain a function for determining font sizes (current, default, preferred or otherwise).

Furthermore, the execution of any function to access delivery context properties is only meaningful where such properties are present in the delivery context. The existence of a function to access a property does not imply that such a property actually exists in the delivery context.

Note, however, that the set of functions based on CSS Media Queries is only a starter set. Extensions that provide additional XPath functions are explicitly allowed and authors are supported in using them. Because other comments have indicated that this may not be clear from the document, DIWG is restructuring the document into two. One deals with the markup and expressions independent from the functions, and the other describes the set of functions.

[1]  <http://www.w3.org/TR/cselection/#sec-starter-set>

Changes to the DISelect document

DIWG does not propose to make any changes to the document as a direct result of this comment. However, as a result of other comments, DIWG does plan to move the discussion of the functions to a separate document. DIWG will take the opportunity to emphasize the fact that this is a minimal starter set of delivery context functions.
Received on Wednesday, 24 August 2005 09:39:18 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 19:41:55 UTC