> >So, to sum it up: "readonly" as attribute is supported in > the current > >version of the styling XSL files, but there will be no > widget support > >for this due to security issues. If treatment of the "readonly" > >attribute should differ from the current situation, it is up to the > >user to modify the styling XSL files. > > > > > > Exactly. Very good summary! > > Furthermore, the choice between readonly/disabled is IMO really a > presentation concern, and not an application concern. That's why I > consider that distinguishing them at the widget level by > introducing an additional state would be useless.
So there is one action left: where do we put this information to inform the original requester and to avoid a recycle of this discussion? Bye, Helma
