search

jakartaee / faces

Jakarta Faces
Other
107 stars 55 forks source link

Only halt component processing on disabled not readOnly #353

Open eclipse-faces-bot opened 16 years ago

eclipse-faces-bot 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]

eclipse-faces-bot commented 5 years ago
eclipse-faces-bot commented 16 years ago

@glassfishrobot Commented Reported by youngm

eclipse-faces-bot commented 16 years ago

@glassfishrobot Commented @rlubke said: Updated target milestone.

eclipse-faces-bot commented 16 years ago

@glassfishrobot Commented rogerk said: Status Whiteboard

eclipse-faces-bot commented 16 years ago

@glassfishrobot Commented @edburns said: effort_moderate

eclipse-faces-bot commented 16 years ago

@glassfishrobot Commented @edburns said: change target_milestone to 2.0

eclipse-faces-bot commented 15 years ago

@glassfishrobot Commented @edburns said: Push to 2.1

eclipse-faces-bot commented 14 years ago

@glassfishrobot Commented @edburns said: Prepare to delete "spec" subcomponent.

eclipse-faces-bot commented 14 years ago

@glassfishrobot Commented @edburns said: Move these to unscheduled because we need to target them correctly. 2.next isn't specific enough.

eclipse-faces-bot commented 14 years ago

@glassfishrobot Commented kito75 said: Changed subcomponent to Components/Renderers.

eclipse-faces-bot commented 14 years ago

@glassfishrobot Commented rogerk said: cat2

eclipse-faces-bot commented 14 years ago

@glassfishrobot Commented @edburns said: These are targeted at 2.1.

eclipse-faces-bot commented 14 years ago

@glassfishrobot Commented sheetalv said: triage

eclipse-faces-bot commented 14 years ago

@glassfishrobot Commented @edburns said: rogerk

eclipse-faces-bot commented 14 years ago

@glassfishrobot Commented rogerk said: target

eclipse-faces-bot commented 14 years ago

@glassfishrobot Commented rogerk said: re-target

eclipse-faces-bot commented 14 years ago

@glassfishrobot Commented rogerk said: For now re-target for 2.2. If time permits may revisit for 2.1.

eclipse-faces-bot commented 13 years ago

@glassfishrobot Commented rogerk said: triage

eclipse-faces-bot commented 10 years ago

@glassfishrobot Commented @edburns said: Set priority to baseline ahead of JSF 2.3 triage. Priorities will be assigned accurately after this exercise.

eclipse-faces-bot commented 10 years ago

@glassfishrobot Commented @manfredriem said: Setting to Major

eclipse-faces-bot commented 7 years ago

@glassfishrobot Commented This issue was imported from java.net JIRA JAVASERVERFACES_SPEC_PUBLIC-353