That's not quite what I was talking about : )
How about just extending buttons with enable/disable and serialize?
(and i.e. keeping getValue/setValue logic consistent)
Are there other ones that would make sense?

- kangax

On May 7, 12:27 pm, John-David Dalton <[EMAIL PROTECTED]>
wrote:
> Patched to work with getValue, 
> setValue.http://github.com/jdalton/prototype/commit/3b03b76660bc29ba5d8a6ef4e0...
>
> Unit 
> tests:http://github.com/jdalton/prototype/commit/101d23d64aba2c0c459c97fa68...
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"Prototype: Core" group.
To post to this group, send email to prototype-core@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/prototype-core?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to