Only halt component processing on disabled not readOnly

alwin-joseph commented 16 years ago

Currently the renderkit docs for input specify that in decode no further processing of a component should take place if it is readOnly or disabled.

I'd like to propose that this get modified to only apply to "disabled". According to (http://www.w3.org/TR/html401/interact/forms.html#adef-readonly) readonly input elements cannot be modified by the user. However, they can be modified by a script and it IS submitted with the form.

For example. You might have a standard "datepicker" JS component. I may attach a javascript datepicker to an inputText component. If I want only the datePicker JS to modify the inputtext then I would set it to "readOnly". This will restrict user modification of the field but allow Script modification. When this form is submitted I would expect JSF to process the date entered using the date picker JS just like it would a non "readonly" input element.

The big difference between disabled and readonly is disabled elements are not submitted with the form.

I would expect JSF to process 'readOnly" elements but not "disabled" elements.

Mike

Environment

Operating System: All Platform: All

Affected Versions

[1.2]

alwin-joseph commented 5 years ago

Issue Imported From: https://github.com/javaee/javaserverfaces-spec/issues/353
Original Issue Raised By:@glassfishrobot
Original Issue Assigned To: Unassigned

alwin-joseph commented 16 years ago

@glassfishrobot Commented Reported by youngm

alwin-joseph commented 16 years ago

@glassfishrobot Commented @rlubke said: Updated target milestone.

alwin-joseph commented 16 years ago

@glassfishrobot Commented rogerk said: Status Whiteboard

alwin-joseph commented 16 years ago

@glassfishrobot Commented @edburns said: effort_moderate

alwin-joseph commented 16 years ago

@glassfishrobot Commented @edburns said: change target_milestone to 2.0

alwin-joseph commented 15 years ago

@glassfishrobot Commented @edburns said: Push to 2.1