Earlier in the week I wrote an article "ColdFusion 11: lists and arrays and empty elements and weird ways to fix stuff", which commented on some poor logic / common sense behind the way Adobe had chosen to fix an issue around how the application setting
this.sameFormFieldsAsArrayworks, in that the array it creates ignores empty form values.
Adobe had claimed "backwards compatibility" on this at the time, but it seems common sense has prevailed: realising that sometimes "being correct" is better than preserving incorrect behaviour for the sake of "backwards compatibility".
Today Himavanth Rachamsetty has added this comment to the ticket:
It seems we were our own worst enemies back in CFMX 6 days (I was on the Prerelease Programme back then, but cannot remember this issue being discussed... I didn't participate in it much), ensuring we were stuck with bung behaviour with the form field list, but Himavanth has seen there's no real backwards compatibility issue to answer to with the newer array option. I don't believe it's a consistency due over ease of use issue though, TBH: it's more a case of not expanding incorrect behaviour when there's no reason to. The list and array cannot cohabitate (as it's an application-wide setting), so there's nothing to be consistent with.
I'd love to see the reasoning the community had with those two old bugtracker issues...
Anyway, good to see Adobe listening to their community / clients!