position-try-order
parsed, no effect: 0 of 2 examples match Chrome
css-anchor-position-1
Our parser accepts the name, yet our rendering is the same with and without the declaration, while Chrome’s changes: on this page the declaration has no effect.
What the specification says
| Initial value | normal |
|---|---|
| Applies to | absolutely positioned boxes |
| Inherited | no |
| Percentages | n/a |
| Computed value | as specified |
| Syntax | normal | <try-size> |
The measurements
2 examples, both render differently. Each is one declaration on a small page, drawn by Chrome and by our engine. Drag on a picture to move the line between them.
position-try-order:most-width, position-try-order:most-inline-size
parsed, no effect

| Pixels that differ from Chrome | 14,400 |
|---|---|
| The same, on the page without the declaration | 0 |
| Largest difference on one colour channel | 187 of 255 |
| The same, on the page without the declaration | 0 of 255 |
Our page is the same with and without the declaration; Chrome’s page changes.
Which values were measured
A match on one example means a match at the value tried. The property’s grammar has 5 branches, and 2 of them carry a measurement.
| Value | Measured |
|---|---|
most-width | parsed, no effect |
most-height | not measured |
most-block-size | not measured |
most-inline-size | parsed, no effect |
normal | not measured |
Measured against Chrome 148.0.7778.96 on 5 November 2026, with up to 40 candidate values tried per property. How it was measured