Every computed style, real stylesheet objects and full 3D geometry, each checked against the reference browser
Scripts that read styles, stylesheets and geometry now get the answers the reference browser gives. getComputedStyle has a value for every CSS property (470 of 475 on a plain element, up from 90), the stylesheet of every style element is a real object that scripts can edit, and the geometry types behind canvas and CSS transforms are full 3D matrices instead of a 2D stand-in. Each one is compared with the reference browser answer by answer, and the matrices are also proven on thousands of generated cases, including against the engine's own CSS transforms. Two engine bugs that could break libraries quietly are fixed on the way.
Every computed style
getComputedStyle is how scripts read the final style of an element: animation libraries, design tools and accessibility checkers all depend on it. Floati used to answer only the properties a page had set, so most reads came back empty. It now answers every property with the reference browser's own value, worked out from what each one depends on (the element's colour, its font, its box), and the work happens once per page, not on every call.
Matrices you can trust
DOMMatrix, DOMPoint and DOMQuad are the maths types behind canvas transforms, CSS transforms and drag and zoom code. Floati's matrix was 2D only and knew four operations; it is now the full 4x4 type with every method, CSS transform strings, 3D rotation and inversion. On every build, 2,200 generated cases check that inverting really inverts, that composing equals applying one after the other, that every matrix survives being written out and read back exactly, and that a transform string gives the same matrix as the engine's own CSS, so what scripts compute and what the page paints cannot drift apart.
What changed 12 changes
Try it in your browser
Each check runs live in the browser you are reading with. Nothing is sent anywhere.