Commit 58be7c08 authored by Gyuyoung Kim's avatar Gyuyoung Kim Committed by Commit Bot

[css-grid] Migrate grid-container-scroll-accounts-for-auto-margin.html to WPT

This CL migrates grid-container-scroll-accounts-for-auto-margin.html
from fast/css-grid-layout to
external/wpt/css/css-grid/alignment with WPT styles,
adding links to the relevant specs, and test description.

Additionally, this test is renamed to
grid-container-auto-margin-scrollbars-001.html to be aligned
with existing tests.

Bug: 1063749
Change-Id: Ib44cdce4fc7c20121efd8cbf0af76cc325a90f1d
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2153449
Commit-Queue: Gyuyoung Kim <gyuyoung@igalia.com>
Reviewed-by: default avatarJavier Fernandez <jfernandez@igalia.com>
Reviewed-by: default avatarManuel Rego <rego@igalia.com>
Cr-Commit-Position: refs/heads/master@{#760293}
parent 9091e417
<!DOCTYPE html> <!DOCTYPE html>
<link rel="match" href="grid-container-scroll-accounts-for-auto-margin-expected.html"> <title>CSS Grid Layout Test: Ignore auto-margins in the track sizing algorithm</title>
<link rel="author" title="Javier Fernandez Garcia-Boente" href="mailto:jfernandez@igalia.com">
<link rel="help" href="https://drafts.csswg.org/css-grid/#alignment"/>
<link rel="help" href="https://drafts.csswg.org/css-grid/#auto-margins"/>
<link rel="issue" href="https://bugs.chromium.org/p/chromium/issues/detail?id=776581"/>
<link rel="match" href="../reference/grid-container-auto-margins-scrollbars-001-ref.html">
<meta name="assert" content="This test ensures that the grid logic ignores any 'auto' margin during the track sizing algorithm. Previously resolved auto-margins should not affect the track sizing computation."/>
<style> <style>
body { body {
display: grid; display: grid;
......
...@@ -6,6 +6,7 @@ body { ...@@ -6,6 +6,7 @@ body {
} }
.item1 { .item1 {
width: fit-content; width: fit-content;
width: -moz-fit-content;
margin: 0px auto; margin: 0px auto;
} }
.item2 { .item2 {
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment