diff options
author | bptato <nincsnevem662@gmail.com> | 2024-11-08 20:45:56 +0100 |
---|---|---|
committer | bptato <nincsnevem662@gmail.com> | 2024-11-08 20:45:56 +0100 |
commit | f6d7c5372b81b9cf7ce76df67b0e61981f96d60f (patch) | |
tree | 7d385e4bd35e4c7209658e6bd99802b1a6b51452 /test/layout/flex-shrink-overconstrained.color.expected | |
parent | b2f70da50f8934fea199150c35c1763e03f72d6d (diff) | |
download | chawan-f6d7c5372b81b9cf7ce76df67b0e61981f96d60f.tar.gz |
layout: fix initial flex item width calculation
Before, the initial layout of a flex item would have inherited the parent's sizing constraint. This almost worked, except when a descendant of a flex item with an unspecified width would resolve its percentage against this incorrectly inherited width - per standard, this must resolve to auto. Also, the shrink case was wrong, because it did not scale the unit to the respective widths; the standard mandates this as well. Hopefully I got it right this time. Finally, this fixes positioned inline container blocks not being set as the absolute container.
Diffstat (limited to 'test/layout/flex-shrink-overconstrained.color.expected')
-rw-r--r-- | test/layout/flex-shrink-overconstrained.color.expected | 6 |
1 files changed, 6 insertions, 0 deletions
diff --git a/test/layout/flex-shrink-overconstrained.color.expected b/test/layout/flex-shrink-overconstrained.color.expected new file mode 100644 index 00000000..82c615f0 --- /dev/null +++ b/test/layout/flex-shrink-overconstrained.color.expected @@ -0,0 +1,6 @@ +[48;2;255;0;0m1111 1111 [38;2;95;95;95m[48;2;255;192;203mtest test test test test [39m[49m +[48;2;255;0;0m1111 1111 [38;2;95;95;95m[48;2;255;192;203mtest test test test test [39m[49m +[48;2;255;0;0m1111 1111 [38;2;95;95;95m[48;2;255;192;203mtest test test test test [39m[49m +[48;2;255;0;0m1111 1111 [38;2;95;95;95m[48;2;255;192;203mtest test [39m[49m +[48;2;255;0;0m1111 [38;2;95;95;95m[48;2;255;192;203m [39m[49m + |