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
Thanks for the answer, I understand the performance drop is a far more
important issue, I just hoped there would be an easy solution.
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({el
On Sat, Mar 5, 2011 at 10:58, andris 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 agre
I'd like to reiterate -- this is going about it backwards.
You do NOT want errors to go undetected.
You do NOT want data that you may have expected to be captured to be
SILENTLY discarded.
You do not want YOUR BUG to be papered over! You want your bugs to be IN
YOUR FACE IN ALL CAPS SHOUTING A
