Skip to content
Changelog

Changelog

Tools shipped, features added, and changes made — newest first.

RSS feed
fixdeveloper

9007199254740993 and 9007199254740992 diffed as identical, because both sides are rounded to the same double before they are compared.

The diff still compares numbers the way JavaScript does, but each source pane now shows a notice when its document contains an integer past 2^53, naming the first one and its line, so a "no changes" result on such data is not taken at face value.

fixtext-data

Integers past 2^53 no longer change silently in either direction.

  • CSV → JSON keeps such values as strings, the same way it already keeps zip codes with leading zeros, and a warning says how many it did that for and where the first one is.
  • JSON → CSV cannot avoid the rounding, since the JSON is parsed before conversion, so it now warns with the original literal, its line, and the value it was rounded to.
fixtext-data

Converting YAML to JSON rounded any integer past 2^53 without comment: id: 9007199254740993 became "id": 9007199254740992.

Validation now reports each such scalar as a warning with its line and column and the value JSON will hold, so you can quote it first if the digits matter. Formatting YAML as YAML is unaffected; the text was never rounded on that path.

fixjson

JavaScript stores numbers as doubles, so any integer past 2^53 (9007199254740991) is rounded the moment it is parsed. 9007199254740993 came out of the formatter as 9007199254740992 with nothing to say it had changed, which is how a database ID gets corrupted while looking perfectly valid.

The formatter now scans the source text, where the digits are still exact, and lists every such integer under Precision warnings with its line and column and the value it becomes. Click one to jump to it. If the exact digits matter, keep the value as a string.

fixtext-data

Three corrections to what the formatter accepts and what it keeps.

  • Bare ampersands and unknown entities are now errors. <r>text & text</r> and <r>&bogus;</r> used to validate as well-formed. A & must now start a character reference or a named entity, and a name must be one of the five predefined entities or be declared in the document's DOCTYPE. Documents that point at an external DTD are given the benefit of the doubt for unknown names. Nothing is decoded; your text is still kept exactly as written.
  • Non-ASCII names are accepted. <é>, <日本語 属性="1"/> and names from the astral planes parse, following the XML 1.0 name productions. The old parser only knew ASCII letters.
  • xml:space="preserve" is honored. Elements marked preserve, and everything inside them, are emitted exactly as parsed instead of being trimmed and re-indented. xml:space="default" on a descendant switches formatting back on for its contents.

If a document you validated before today contained a bare &, it will now be flagged. That is the tool catching up with XML, not a regression.

fixtext & data

The autosave label read Saved · just now whether or not the browser had actually stored the document. When local storage is blocked or full (private browsing, a filled quota), the write failed quietly, the label advanced anyway, and a refresh would have lost the text.

A save that storage refuses now shows Not saved · storage unavailable instead, the timestamp stays where it was, and the next keystroke tries again. The document stays in memory for the session either way; if it matters, use the download action to keep a copy.

fixtext-data

Three inputs that used to lose cells with no warning now keep everything and say what happened.

  • Duplicate headers. A header row of a,a,a (2) named the second column a (2), the same as the third, and the third overwrote it. Numbering now skips any name that already appears in the header, so those columns become a, a (3) and a (2). The CSV Explorer shares this naming code and gets the same fix.
  • Ragged rows. A row with more cells than the header dropped the extras. They are now kept under Column 3, Column 4 and so on, and a warning reports how many rows were wider and where the first one is.
  • Flatten collisions. With Flatten nested on, {"a.b":1,"a":{"b":2}} produced a single a.b column holding 2. Both values are kept, the second as a.b (2), with a warning naming the row.

If you exported from one of these inputs before today, it is worth converting it again.

fixcolor

The two swatches either side of your base color were labeled Analogue. The scheme is analogous, the color-theory term for hues next to each other on the wheel, and "analogue" is a different word. The label is now correct.

This changes exported output, because the label becomes part of the Tailwind @theme block: --color-analogue-minus-30 and --color-analogue-plus-30 are now --color-analogous-minus-30 and --color-analogous-plus-30. If you already pasted a generated block into a project, update those two token names. The hex values are unchanged.

new toolbetaadvanced-local

Gamepad Tester shows what your controller is doing as you use it. It ships in beta, because controller hardware varies a lot and the tool is still meeting new pads.

Plug in a controller, press a button, and a diagram lights up in real time: sticks that move and click, bumpers, d-pad directions, and every face and menu button.

The diagram uses your controller's own labels. It detects which console family the pad belongs to and renames everything to match, with shape glyphs on one family, LB/RB/View/Menu on another and the swapped B/A/Y/X lettering on the third. You can also view any pad with any of the three naming styles.

Each stick shows its raw reading and its deadzone-adjusted position at once, so a dot that won't sit at center reveals stick drift. Set the deadzone to off, a light 5%, or the 15% a typical game uses, and the boundary is drawn on the stick plot. Triggers, stick clicks, d-pad directions and per-button analog values update live, and pads that support rumble get a vibration test button. Controllers without the standard layout get plain numbered buttons and raw axis bars instead of made-up labels.

No controller handy? A demo pad moves the sticks and presses every button so you can explore the tool. Controller input never leaves your browser.