Hashing a file ran all four digests at once, each with its own copy of the file, so a file near the old 512 MB limit could need about 2.5 GB and crash the tab. The digests now run one after another, and the file limit is 256 MB.
Changelog
Tools shipped, features added, and changes made — newest first.
RSS feedInput that only looked vaguely like a date was handed to the browser's lenient date parser, so hello 2 became 1 February 2001 and Order 12 became 1 December 2001, both labelled RFC 2822.
Free-form dates are now only accepted when they contain a four-digit year or an English month name, and anything else is reported as unrecognized.
In local time, the next runs were computed without regard to daylight saving, so around a clock change the list could repeat times, go backwards, or include runs earlier than now.
Next runs now follow cronie: a job fixed to a time in the skipped hour runs once right after clocks spring forward, a job with * in its minute or hour skips times that do not exist, and the list is always strictly increasing and after now.
A day-of-month or day-of-week field that starts with *, such as */2, now means both day fields must match, as in Vixie cron and cronie, and the description says so: 0 0 */2 * 1 runs on odd days that are also Mondays.
Every visitor used to see the same five UUIDs when the page loaded. The first batch is now freshly random each time you open the page.
Version 7 UUIDs generated in the same millisecond now sort in the order they were made. If your browser has no secure random source, the tool says so instead of quietly using a weaker one.
Base64 decoding rejected the URL-safe alphabet, so PDw_Pz8-Pg was reported as invalid even though it is ordinary base64url. Decoding now accepts - and _ and input with the trailing = padding left off.
With the u or v flag, a pattern that can match an empty string (such as \w* or \p{L}?) got stuck just before an emoji and repeated the same match until the 5,000-match limit. It now finds the same matches as JavaScript's matchAll.
A new run that replaced one still in progress could be stopped early with a false "too slow" error. Each run now gets its own time limit. Named groups are no longer highlighted twice.
The CSP grade looked for unsafe-inline or unsafe-eval anywhere in the header text, so 'wasm-unsafe-eval' and strict nonce-based policies with an 'unsafe-inline' fallback for old browsers were graded weak.
The grade now reads the policy's actual sources, and ignores 'unsafe-inline' when a nonce or hash makes browsers ignore it too.
Directive names and keywords were matched case-sensitively, but CSP treats them case-insensitively, so Script-Src 'self' was reported as unrecognized and as missing a script-src, and 'Unsafe-Inline' went unflagged.
They are now recognized whatever their case. A directive that appears twice no longer produces two warnings that confused the summary.
A token whose exp, iat or nbf claim was beyond the range JavaScript dates can hold (for example "exp": 1e13) crashed the decoder. Such claims now read Out of the representable date range, and the token's expiry status is still worked out.
The verification sweep animation now stays still when your system asks for reduced motion.
Only the element itself was checked for being hidden, so controls inside a hidden or display: none parent, an inert parent, or a closed <details> were listed as tabbable.
Those are now left out (a closed <details> keeps its summary). A tabindex that is not a number, such as tabindex="abc", now counts as absent, as browsers treat it. And disabled now only applies to form controls, so <a href disabled> stays in the order, while controls inside a disabled <fieldset> are left out.