On Mar 3, 2011, at 2:40 AM, andris wrote:
> The question is, should Prototype address it or is it a developers
> problem? Isn't the work of a JS library to smooth out these kind of
> inconsistencies - for example either falling back to a non native
> encoder with WebKit or forcing other browser to
It will feel SO much better when you stop!
I can't see supporting serializing host objects, ever.
But I could support doing something to make it ALWAYS error. It IS the
developer's problem, but sometimes it helps to have one's mistakes pointed
out to you promptly, before you go public...
On Thu,
Hi,
Native JSON encoding in WbKit based browsers is a bit different from
the others - if an object that is being encoded contains a host object
(DOM elements etc.), then the encoding fails and a TypeError is cast.
When other browsers simply skip host objects (treated as being empty
"{}"), then We
