Suffix added to a namespaced <select> name can mess up request parameters

[GoogleCodeExporter]

Consider a HTML select named "foo[bar]". Now with submitFreeText == true, a 
suffix is added to the name => "foo[bar]_ufd". This can mess up request 
parameters on the server side.

The correct way to add a suffix would be "foo[bar_ufd]".

Original issue reported on code.google.com by zabojnik...@gtempaccount.com on 12 Apr 2010 at 1:13

[GoogleCodeExporter]

Thanks for reporting, you are correct, to fix.

Original comment by thetoolman on 23 Apr 2010 at 7:56

• Changed state: Accepted

[GoogleCodeExporter]

Interestingly, they are technically invalid: 

http://www.w3.org/TR/html401/types.html#type-name

'ID and NAME tokens must begin with a letter ([A-Za-z]) and may be followed by 
any
number of letters, digits ([0-9]), hyphens ("-"), underscores ("_"), colons 
(":"),
and periods (".").'

Original comment by thetoolman on 23 Apr 2010 at 7:58

[GoogleCodeExporter]

but they are used in Spring for collections, and other tools undoubtedly, will 
make
it SB aware.

Original comment by thetoolman on 23 Apr 2010 at 7:59

[GoogleCodeExporter]

Instead of suffixing the content in square brackets, which might cause issues 
with
numeric brackets I'll switch to prefixing, which wont interfere.

Original comment by thetoolman on 23 Apr 2010 at 8:09

[GoogleCodeExporter]

In trunk, will be included in upcoming v0.6

Original comment by thetoolman on 23 Apr 2010 at 8:15

[GoogleCodeExporter]

Original comment by thetoolman on 23 Apr 2010 at 8:15

• Changed state: Verified

[GoogleCodeExporter]

Issue 18 has been merged into this issue.

Original comment by thetoolman on 6 May 2010 at 11:05

[GoogleCodeExporter]

Line 45 in the new version should be:

var prefixName = this.options.prefix + selectName;

Original comment by tjeerd.m...@gmail.com on 8 May 2010 at 11:27