This is somehow annoying as this library usage seems to be increasing and also because it's a valid correctness test which is failing with a reason.įinally, for strict web services which start to adopt this 'new' format for Date object serializing into JSON, this issue may cause content including extended years (which are arguably rare, but that's my experience) to be discarded for this reason.Īs a side note, the under-specification of 'toISOString' issue, stated in comment #0, is already addressed and properly marked as 'fixed'. Even though there are plenty of better tools out there like Rufus to create bootable USB from an ISO file, most PC users prefer using the official Windows 7 USB/DVD Download Tool. (On the other hand, negative extended dates seem to be properly working in this scope.) These days, a large number of PC users prefer installing Windows OS from a USB drive instead of traditional DVD disc.

This causes Firefox to serialize the date as '27T00:00:00.000Z', thereby missing the positive sign, which is mandatory in extended years according to ES5.1 - 15.9.1.15.1. When trying to understand why the JSON3 library partially 'failed' in Firefox, falling-back to a script-based implementation for the 'stringify' part (the 'parse' seems to be properly working, though), I noticed that the particular test (here simplified) which made the correctness of the API fail was similar to: Marking as 'new' due to the already confirmed cases and my own.

Not a valid iso file