W3C home > Mailing lists > Public > www-forms@w3.org > October 2002

Re: readonly and setvalue

From: Mikko Honkala <honkkis@tml.hut.fi>
Date: Mon, 07 Oct 2002 11:42:08 +0300
Message-ID: <3DA148E0.4040401@tml.hut.fi>
To: "Tomayko, Ryan" <Ryan_Tomayko@stercomm.com>
CC: Jérôme Nègre <jerome.negre@e-xmlmedia.fr>, Micah Dubinko <MDubinko@cardiff.com>, "'bhanu'" <bhanu_k@hotmail.com>, www-forms@w3.org

Hi Tomayko,

very good point. I have implemented "readonly" similarly. I have also 
made demos with similar functionality as you describe.

In my opinion, this is so important feature that the spec should not 
retrict the processor to change values marked "readonly". "readonly" 
should affect just the UI. It seems that at least 3 implementors have 
implemented it that way for a reason.

-mikko

Tomayko, Ryan wrote:
> Another example of why you would want readonly only to apply to the UI is
> calculating values. For instance, you my want to display a list of product
> line items and allow the user to input the quantity and unit price for each.
> The line total would be readonly and calculated based on the quantity * unit
> price.
> 
> - Ryan Tomayko
> 
> 
> -----Original Message-----
> From: Jérôme Nègre [mailto:jerome.negre@e-xmlmedia.fr] 
> Sent: Monday, October 07, 2002 3:07 AM
> To: Micah Dubinko
> Cc: 'bhanu'; www-forms@w3.org
> Subject: Re: readonly and setvalue
> 
> 
> 
> Hi,
> 
> 
>>Good question! Does 'readonly' mean readonly-to-user, or
>>readonly-to-everything?
>>
>>Implementers, how did you handle this?
> 
> 
> Here, for XFE, we chose readonly-to-user. That way, one can have a 
> select or a range showing data without the possibility for the user to 
> change it.
> 
> Regards,
> Jérôme
Received on Monday, 7 October 2002 04:45:05 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Saturday, 10 March 2012 06:21:53 GMT