The main issue was that it was esoteric and inconsistent. First, all our
.getFoo methods in 1.2 changed to .get('foo') - get('html'), get('value'),
etc. But this method quite explicitly returns either the property of an
element or the value for a custom getter (such as get('tween') which returns
the built in instance of Fx.Tween).
getValue changed to get('value'), but now it does exactly what it does for
all other element properties - it just returns the value property. The
problem with getValue is that it returned the value for *some* things, but
returns other things for other things. Select lists returned the value or
values of the selected properties, which meant it returned strings sometimes
and arrays other times. But for radio buttons, if I recall, it returned the
value property, and not the value that was selected. Same with checkboxes.
This kind of inconsistency was something we just didn't want to support.
It's far better to write code that returns something that is predictable.
On Mon, Jan 11, 2010 at 10:29 AM, Offroadcode <[email protected]
> wrote:
> Just been working on a new site which does not have the backwards
> compat installed and realised that .getValue() no longer exists for
> the first time. Its been replaced for select lists with the long
> winded .getSelected()[0].value
>
> Just wondering if anyone knew why this was dropped? Its a handy bit of
> code (easy enough to add back in myself I know).
>
> Cheers
>
> Pete
>
