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

Re: [css3-ui] Problems with :read-only and :read-write (was [WF2] Readonly and default pseudoclass matching)

From: Orion Adrian <orion.adrian@gmail.com>
Date: Mon, 1 Aug 2005 16:07:03 -0400
Message-ID: <abd6c801050801130794ec167@mail.gmail.com>
To: www-style@w3.org

> > Editors may want to only allow editing of part of the document at a time too...
> 
> Did you really mean "editors" (computer programs).  I thought the main
> demand for this came from corporate IT or marketing departments and
> is basically the same issue that results in content management systems
> when HTML was intended to be authored by content creators.
> 
> (I could also imagine it being used for bulletin board systems, but
> that would require treating the editable portion as a rich text control
> on a form and posting it to the server.  As such rich text controls
> would almost certainly be used purely presentationally, the use of HTML
> should probably not be encouraged.)

Let me clarify, I was very tired. Site/content managers may want to
control what is accessible. A good example of that today would be Wiki
where ther is control over who has access to what and when. Either the
client will have to include control over this or the server will. If
the client does it, it will have to know about the users and
permissions involved. If it's done at the server, it will require what
it already requires. What I'm asking is what does contentEditable get
us that we don't already have? Does it make document management
easier?

-- 

Orion Adrian
Received on Monday, 1 August 2005 20:07:16 GMT

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