Ptree is drawn by the browser’s own layout, cascade, and animation engines, written to current web standards without a framework. Where an engine misreads a standard, or has not shipped one yet, Ptree reads around it in the smallest way that keeps the native path intact, and removes that reading once the engine ships. Each defect Ptree finds is reported to the engine with a reduced test case. The issues below are the ones Ptree handles today.
Chrome and Edge (Chromium)
- A scoped view transition aborts when its update removes a named element
- An
Element.startViewTransition()whose update callback removes a descendant carrying aview-transition-namerejectsreadywithInvalidStateError“Prepaint layout check failed”: 40 of 50 trials in Chrome 155 and 31 of 50 in Edge 155, whiledocument.startViewTransition()with the same removal resolves every time. Ptree reported it with a test case on October 21, 2026 (Chromium issue 576097103). - A column leaving the comparison panel stays laid out, inert, invisible, and unnamed until the transition is ready, and is removed then.
- Fixed in Chromium on October 22, 2026, the day after the report; first in Chrome 158. The retained column goes once supported Chrome versions carry the fix.
:checkeddoes not match an indeterminate checkbox- A checkbox that is both checked and indeterminate matches
:checkedin Firefox and Safari but not in Chrome. HTML keeps the two states independent; the Selectors specification calls them exclusive. The CSS Working Group has not settled which prevails (csswg-drafts issue 9706, on the TPAC 2026 agenda). - Wherever checkedness is what matters, as for the location filter while a place is being picked, Ptree selects on
:is(:checked, :indeterminate).
Safari (WebKit)
anchor()re-reads a scrolled anchor’s live offset on any style change- Safari 26 keeps a non-default anchor’s remembered scroll offset while its scroller moves, but the next style change on the positioned element, even to an unrelated custom property, resolves
anchor()against the live offset, so the element jumps by the scrolled distance. Safari 18, Chrome 155, and Firefox 158 keep the remembered offset, as CSS Anchor Positioning requires. Ptree reported it with a test case on October 20, 2026 (WebKit bug 328291); WebKit confirmed it in Safari Technology Preview 254. - The Icicle’s connector between two selected tiles takes each tile’s live edge from its view timeline rather than from a corrected
anchor(), which reads the same in every engine. - A grid placed by
position-areais sized to the whole area below its anchor - Safari 26.4 and 26.5 stretch the auto rows of a
position-areapopover laid out as a grid into the entire block-end area below its anchor, then size the popover to those rows: 982px tall for 126px of content on a 1080px screen. The same content as a wrapping flex row, or the same grid in flow, is sized to its content, as Chrome 155 and Firefox 158 size the grid popover. Ptree reported it with a test case on October 23, 2026 (WebKit bug 328749). - The print menu is a wrapping flex row, which every engine sizes to its buttons.
- An anchor-positioned element ignores its anchor’s transform
- Safari 26.4 positions an element against its anchor’s untransformed box, so a label anchored to a translated glyph lands beside the wrong point (WebKit bug 313104).
- The diamond marking a lone value on a numeric scale is centered by subtracting half its size from its insets instead of by a translate.
- Fixed in WebKit on April 29, 2026. The translate returns once supported Safari versions carry the fix.
- An iframe’s
light-dark()colors follow the system theme, not the frame’scolor-scheme - WebKit can match an iframe’s dark-mode media query from the parent document’s
color-schemewhilelight-dark()in the same frame still answers the system theme; Chrome and Firefox keep the two together (WebKit bug 316680, open). The disagreement cannot be detected with@supports. - The Wikipedia reader tests once whether the two disagree and, only then, sets each article’s color scheme directly.
Standards not yet in every browser
- Scroll-driven animations
- Firefox ships view timelines in version 159 (Firefox bug 1324602); Chrome has them since 115 and Safari since 26.
- In Firefox the Icicle’s connector takes the selected tiles’
anchor()edges, exact at each selection and still while a column scrolls until the next one. - Typed arithmetic in
calc() - Dividing one length by another to get a number reaches Firefox in version 158 (Firefox bug 2067411); Chrome has it since 140 and Safari since 26.
- Until then Firefox counts the views’ columns and scales the Cladogram’s bars through
tan(atan2()), which cancels two lengths without dividing them. - State-preserving DOM moves
Element.moveBefore()is in Chrome 133 and Firefox 144; WebKit’s implementation is in progress (WebKit bug 281223).- In Safari, columns and comparison subjects are reordered through
insertBefore(), which keeps the order working but restarts the moved element’s state. - Light dismissal of dialogs
- The
closedbyattribute, which lets a click outside a dialog close it, is in Chrome 134 and Firefox 141 and in Safari Technology Preview (WebKit bug 284592). - Where the attribute is absent, a click on the expanded photo or map that lands on no content, which can only be the backdrop or the dialog’s own unpainted box, requests the close the attribute would.
- Iterating a stream
- A fetched reply’s body can be read with
for awaitin Chrome and Firefox; WebKit has implemented it (WebKit bug 194379), but Safari 26 doesn’t ship it yet. - In Safari, the question box reads its answer through the stream’s reader one piece at a time, which plays the tour the same way.
- Unprefixed
user-select - Safari still reads only
-webkit-user-select; the standard name is in Safari Technology Preview (WebKit bug 208677, open since 2020). - Ptree declares the prefixed property beside the standard one.
stretchsizing- The
stretchkeyword is in Chrome 138 and in Safari 27 (WebKit bug 277117, fixed March 2026); Firefox keeps it behind a preference (Firefox bug 1789477). Both accept the older-webkit-fill-available. - Comparison readout cells fill their row through the older name, and the connector drawing above the table takes its height from a script that resolves the same CSS insets the stretched box would.
- Gap decorations
- Rules drawn in a grid’s row gaps are in Chrome 149; Firefox (bug 1963897) and WebKit (bug 298551) have not implemented them.
- Comparison readout rows draw their dividing lines as cell borders, each cell stretched to its row so the line meets the row’s end however its neighbors wrap. Once every engine draws row rules, the cells’ borders and their stretch sizing go.
interactivity: inert- Chrome has the property since 135; Firefox (bug 1943864) and WebKit (bug 288202) have not implemented it.
- Hidden, departing, and not-yet-loaded taxa also carry
pointer-events: none, the hit-testing half of inertness that those engines still need. - Scroll buttons
- Native
::scroll-button()pseudo-elements are in Chrome 135; Firefox (bug 1964448) and WebKit have not implemented them. - Where the property menu cannot draw native scroll buttons, Ptree keeps its own previous and next buttons, each labeled with the neighboring column, and hides them where the native ones exist.
border-shape- Shaping a box’s border, background, and outline together is in Chrome 147; Firefox (bug 1982766) and WebKit (bug 320627) have not implemented it.
- The tree’s chevrons are cut with
clip-pathas well, so their shape survives without the shaped border; a backbone’s tooltip is a plain box. display: math- The math display type is in Chrome 109; Firefox and WebKit (bug 278533) render MathML without it.
- A property readout’s MathML unit is sized and centered by hand where the display type is missing.
text-justify- Inter-character justification is in Chrome 145 and Firefox 55; WebKit has not implemented it (bug 99945).
- The imprint’s address justifies its lines only where the property exists.