- From: Allan Beaufour <abeaufour@novell.com>
- Date: Thu, 01 Sep 2005 23:20:50 +0200
- To: <www-style@w3.org>
Ons, aug 17, 2005 kl. 8:24 pm skrev Matthew Raymond <mattraymond@earthlink.net> i meddelelse <430380C1.2020906@earthlink.net>: > | 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. I've thought some more about this, and the above is what is meant in an XForms content. It also mimics how :enabled/:disabled works for HTML content, because that is also tied closely together with an attribute on the element. So maybe having an :editable selector wouldn't be such a bad idea. If you are designing a form, based on an editor template where you can only edit some parts of the form, the form would have parts that are :editable by you and some that are not. Input fields can be styled depending on whether they will be :read-only or :read-write to the user, no matter the :editable state of the part they live in. -- Allan Beaufour, Novell Denmark Novell® BrainShare® Barcelona 2005 11-15 September The CCIB, Barcelona, Spain www.novell.com/brainshare/europe
Received on Thursday, 1 September 2005 21:21:20 UTC