W3C home > Mailing lists > Public > www-style@w3.org > August 2005

Re: Request for specific changes to CSS3-UI

From: Matthew Raymond <mattraymond@earthlink.net>
Date: Wed, 17 Aug 2005 14:24:01 -0400
Message-ID: <430380C1.2020906@earthlink.net>
To: Allan Beaufour <abeaufour@novell.com>
CC: www-style@w3.org

Allan Beaufour wrote:
> On Tuesday 16 August 2005 23:14, Matthew Raymond wrote:
> 
>>| The purpose of the :read-only and :read-write pseudo-classes is to
>>| allow authors to customize the look of elements which have a
>>| "read-only" property or attribute that can be set in the markup. An
>>| element is :read-only if its "read-only" property or attribute is set
>>| to true. An element is :read-write if its "read-only" property or
>>| attribute is set to false.
> 
> XForms elements do not have a readonly property or attribute that can be set 
> directly on the element itself. Controls are bound to data nodes, which have 
> a readonly property. So as I read it, the above is not valid for XForms.

  Okay, let me try again:

| The purpose of the :read-only and :read-write pseudo-classes is to
| allow authors to customize the look of elements which have a
| read-only property or attribute, or are otherwise bound to a node
| with a read-only model item property, that can be set in the
| markup. An element is :read-only if its associated "read-only"
| property or attribute is set to true. An element is :read-write if its
| associated "read-only" property or attribute is set to false.

   Better?
Received on Wednesday, 17 August 2005 18:24:08 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Monday, 27 April 2009 13:54:40 GMT