position-try-fallbacks
parsed, no effect: 0 of 12 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 | none |
|---|---|
| Applies to | absolutely positioned boxes |
| Inherited | no |
| Percentages | n/a |
| Computed value | as specified |
| Syntax | none | [ [<dashed-ident> || <try-tactic>] | <position-area> ]# |
The measurements
12 examples, all 12 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-fallbacks:flip-block, position-try-fallbacks:flip-y, position-try-fallbacks:top, position-try-fallbacks:y-start, position-try-fallbacks:self-y-start, position-try-fallbacks:block-start
parsed, no effect

| Pixels that differ from Chrome | 14,400 |
|---|---|
| The same, on the page without the declaration | 7,200 |
| Largest difference on one colour channel | 204 of 255 |
| The same, on the page without the declaration | 204 of 255 |
Our page is the same with and without the declaration; Chrome’s page changes.
position-try-fallbacks:left, position-try-fallbacks:x-start, position-try-fallbacks:self-x-start
parsed, no effect

| Pixels that differ from Chrome | 13,798 |
|---|---|
| The same, on the page without the declaration | 7,200 |
| Largest difference on one colour channel | 204 of 255 |
| The same, on the page without the declaration | 204 of 255 |
Our page is the same with and without the declaration; Chrome’s page changes.
position-try-fallbacks:right, position-try-fallbacks:x-end, position-try-fallbacks:self-x-end
parsed, no effect

| Pixels that differ from Chrome | 13,798 |
|---|---|
| The same, on the page without the declaration | 7,200 |
| Largest difference on one colour channel | 204 of 255 |
| The same, on the page without the declaration | 204 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 57 branches, and 12 of them carry a measurement. At most 12 examples are published per property, so a branch past that is left out by our choice.
| Value | Measured |
|---|---|
--flexpdf | not measured |
flip-block | parsed, no effect |
flip-inline | not measured |
flip-start | not measured |
flip-x | not measured |
flip-y | parsed, no effect |
left | parsed, no effect |
center | not measured |
right | parsed, no effect |
span-left | not measured |
span-right | not measured |
x-start | parsed, no effect |
x-end | parsed, no effect |
span-x-start | not measured |
span-x-end | not measured |
self-x-start | parsed, no effect |
self-x-end | parsed, no effect |
span-self-x-start | not measured |
span-self-x-end | not measured |
span-all | not measured |
top | parsed, no effect |
bottom | not measured |
span-top | not measured |
span-bottom | not measured |
y-start | parsed, no effect |
y-end | not measured |
span-y-start | not measured |
span-y-end | not measured |
self-y-start | parsed, no effect |
self-y-end | not measured |
span-self-y-start | not measured |
span-self-y-end | not measured |
block-start | parsed, no effect |
block-end | not measured |
span-block-start | not measured |
span-block-end | not measured |
inline-start | not measured |
inline-end | not measured |
span-inline-start | not measured |
span-inline-end | not measured |
self-block-start | not measured |
self-block-end | not measured |
span-self-block-start | not measured |
span-self-block-end | not measured |
self-inline-start | not measured |
self-inline-end | not measured |
span-self-inline-start | not measured |
span-self-inline-end | not measured |
start | not measured |
end | not measured |
span-start | not measured |
span-end | not measured |
self-start | not measured |
self-end | not measured |
span-self-start | not measured |
span-self-end | not measured |
none | 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