- From: Patrick Lauke <P.H.Lauke@salford.ac.uk>
- Date: Mon, 19 Sep 2005 15:35:22 +0100
- To: <www-style@w3.org>
> Gavin Kistner > But now you're tempting me, because I really would like to be > able to > use CSS to shove ancillary sidebar content as footnotes and create > links to it. But should this not be behaviour that is taken care of by the user agent? We'd need a way to define (in content?) that something is ancillary information such as a footnote, but leave it up to the browser to decide how best to deal with it based on user preference, device capabilities, etc > Should CSS be able > to decide whether a list of items should be rendered as radio > buttons > versus a drop-down select? That, to me, stradles the concepts of presentation and behaviour...I can see pros and cons on both sides in this particular instance. Again though, in an ideal situation the list of items would be marked up in content as being such a list, and the decision on how it should be exposed to the user (both in terms of how the list looks, and how the user can interact with it) should be left to the user agent (but yes, possibly with hints provided by the author). Patrick __________________________________________________________ Patrick H. Lauke Webmaster / University of Salford http://www.salford.ac.uk __________________________________________________________ Web Standards Project (WaSP) Accessibility Task Force http://webstandards.org/ __________________________________________________________
Received on Monday, 19 September 2005 14:31:49 UTC