Hi Radoslav,
Thanks for reply, I have indeed did something very similar to this,
just some different terminology
plus i have wrapped the Form.Element.setValue method to fire
'value:changed' event too.
You might wanna do that too if you are initializing your form elements
with some default values o
hm, I have similar problem (in my case I was adding / removing a lot
of inputs dynamically). And using Form.Observer / Element.observe
would have been an small maintenance hell. So I have been using 2
custom events - focus:in / focus:out, for bubbling focus/blur.
http://gist.github.com/162593
Yo
Hi Tobie,
It is a monstrous form that i am dealing with indeed.
It is composed of several collapsable and repeatable sections.
As a starter, the form has around 50 inputs, but in some extreme use
cases, the total number of inputs may reach 800 :-o
thanks for the tip
cheers
--
mona
On Mon, Aug
None of my business... but you're certainly doing something wrong UI-
wise if you have 100s of inputs on the same page.
Best,
Tobie
On Aug 31, 1:15 pm, Mona Remlawi wrote:
> oh that would be a big overhead for me as the forms i'm talking about
> can grow to have 100s of inputs.
> so serializin
oh that would be a big overhead for me as the forms i'm talking about
can grow to have 100s of inputs.
so serializing to detect changes doesn't seem to be a good idea,
neither having TimedObservers on Form.Element level.
guess my best option is to set the onchange attribute on input
elements to t
Hi Mona,
Have you considered using Form.Observer[1] instead of events?
[1] http://prototypejs.org/api/timedObserver/form-observer
--
T.J. Crowder
tj / crowder software / com
www.crowdersoftware.com
On Aug 31, 10:07 am, Mona Remlawi wrote:
> Hello Prototypers,
>
> I am currently in the process
