Chromium Code Reviews
chromiumcodereview-hr@appspot.gserviceaccount.com (chromiumcodereview-hr) | Please choose your nickname with Settings | Help | Chromium Project | Gerrit Changes | Sign out
(153)

Unified Diff: third_party/WebKit/LayoutTests/platform/win/fast/replaced/table-percent-height-text-controls-expected.txt

Issue 2535173006: Percent height border-box content should get correct height in percent height cells (Closed)
Patch Set: bug 669867 Created 4 years ago
Use n/p to move between diff chunks; N/P to move between comments. Draft comments are only viewable by you.
Jump to:
View side-by-side diff with in-line comments
Download patch
Index: third_party/WebKit/LayoutTests/platform/win/fast/replaced/table-percent-height-text-controls-expected.txt
diff --git a/third_party/WebKit/LayoutTests/platform/win/fast/replaced/table-percent-height-text-controls-expected.txt b/third_party/WebKit/LayoutTests/platform/win/fast/replaced/table-percent-height-text-controls-expected.txt
index 6a84efd4100f2313e21607fec0ab9bf74b8c090c..9a2f2e3284e95dfa8762fca37b24fd81ca2c7619 100644
--- a/third_party/WebKit/LayoutTests/platform/win/fast/replaced/table-percent-height-text-controls-expected.txt
+++ b/third_party/WebKit/LayoutTests/platform/win/fast/replaced/table-percent-height-text-controls-expected.txt
@@ -4,7 +4,7 @@
-This test checks that text controls with percentage heights within table cells have the correct height.Text controls are in a different test than other replaced elements because their metrics are platform-specific.
+This test checks that text controls with percentage heights within table cells have the correct height.Text controls are in a different test than other replaced elements because their metrics are platform-specific.The reason a 75% control is the same height as a 100% control is because a replaced element that depends on theheight of its parent cell is treated as auto. So by itself it will set the height of the row. See https://drafts.csswg.org/css-tables-3/#row-layout
On success, you will see a series of "PASS" messages, followed by "TEST COMPLETE".
@@ -14,13 +14,13 @@ PASS successfullyParsed is true
TEST COMPLETE
PASS getWidth('input-password-75') is getWidth('input-password-100')
PASS getFullHeight('input-password-75') != '0px' is true
-FAIL getFullHeight('input-password-75') [16.5px] is not 75% of getFullHeight('input-password-100') [22px].
+PASS getFullHeight('input-password-75') is getFullHeight('input-password-100')
PASS getWidth('input-text-75') is getWidth('input-text-100')
PASS getFullHeight('input-text-75') != '0px' is true
-FAIL getFullHeight('input-text-75') [16.5px] is not 75% of getFullHeight('input-text-100') [22px].
+PASS getFullHeight('input-text-75') is getFullHeight('input-text-100')
PASS getWidth('textarea-75') is getWidth('textarea-100')
PASS getFullHeight('textarea-75') != '0px' is true
-PASS getFullHeight('textarea-75') is 75% of getFullHeight('textarea-100').
+PASS getFullHeight('textarea-75') is getFullHeight('textarea-100')
PASS successfullyParsed is true
TEST COMPLETE

Powered by Google App Engine
This is Rietveld 408576698