On Sat, Mar 5, 2011 at 10:58, andris <andris.rein...@gmail.com> wrote:
>
> But just to be clear - I didn't want Prototype to force *other*
> browsers to behave as WebKit but to force WebKit to behave as others.
> So when I do Object.toJSON({elm:HTMLDIVElement}) it wouldn't end on
> error but with {elm:{}} instead.
I agree with Andrew that Prototype shouldn't do anything in this regard.
You've got a good point that it's the job of a JS library to smooth out such
inconsistencies, but any meddling in this case would result in slowdowns.
There could exist a Prototype plugin which performs a simple traversal of
the array/hash before sending it to JSON encoder, and if it finds properties
that reference DOM elements it could blank those out. Someone whose JS app
suffers from these DOM references creeping in their JSON data might want to
use such plugin.
--
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
prototype-core-unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/prototype-core?hl=en
