[JAVASERVERFACES_SPEC_PUBLIC-418] autocomplete is missing on form component Created: 07/Jul/08  Updated: 01/Aug/14  Resolved: 24/Jan/14

Status: Closed
Project: javaserverfaces-spec-public
Component/s: Components/Renderers
Affects Version/s: 2.0
Fix Version/s: 2.2

Type: Bug Priority: Major
Reporter: mwessendorf Assignee: Unassigned
Resolution: Duplicate Votes: 3
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Operating System: All
Platform: All

Issuezilla Id: 418
Status Whiteboard:

cat2 renderkitdoc size_medium importance_large


Not only <input> allows the autocomplete property.
We should have that on the form as well:

See here for details:

This is broken in JSF 1.1, JSF 1.2 and 2.0 EDR

Comment by mwessendorf [ 19/Aug/08 ]

see https://javaserverfaces-spec-public.dev.java.net/issues/show_bug.cgi?id=322

Comment by rogerkeays [ 26/Aug/08 ]

AFAICT autocomplete is not a valid attribute for forms OR inputs in HTML4.01


Comment by pmuir [ 27/Aug/08 ]

http://www.w3.org/Submission/web-forms2/ - it's not finalised yet, but it is
supported (IE, Mozilla)

Comment by mwessendorf [ 27/Aug/08 ]

Roger: it is already present in <h:inputText/>. When you do ajax (or some other
client side stuff), you want to have an option to say autocomplete=OFF.
A general rule for this is on the form.

The problem with the browser-build-in "autocomplete" feature is:
-user enters a value by using the suggested value from the browser "feature".
-now TABs out => no!!! change event is fired
-also scorecard style apps really don't want that.

Form is pretty much wanted instead of disabling of on 100 inputText components

Comment by Ed Burns [ 24/Sep/09 ]

Move to unscheduled target milestone

Comment by Ed Burns [ 24/Nov/09 ]

Prepare to delete api subcomponent

Comment by kito75 [ 24/Feb/10 ]

Change subcomponent to Components/Renderers.

Comment by kito75 [ 24/Feb/10 ]

Scheduled for 2.0 Rev A.

Comment by Ed Burns [ 03/Mar/10 ]


Comment by Ed Burns [ 22/Mar/10 ]


Comment by Ed Burns [ 15/May/10 ]

These are targeted at 2.1.

Comment by rogerk [ 17/Jun/10 ]


Comment by Ed Burns [ 22/Jun/10 ]

Move up to importance_large

Comment by Ed Burns [ 24/Jun/10 ]

GlassFish 3.1 M6 at the latest.

Comment by Ed Burns [ 10/Sep/10 ]

Move these to 2.2

Comment by Ed Burns [ 24/Jan/14 ]


Comment by Manfred Riem [ 01/Aug/14 ]

Closing resolved issue out

Generated at Sun Apr 30 19:43:51 UTC 2017 using JIRA 6.2.3#6260-sha1:63ef1d6dac3f4f4d7db4c1effd405ba38ccdc558.