Tanks for filing the issue...

Unable to reproduce the issue on reported chrome version 73.0.3662.0 using Mac 10.14.0. Attaching screenshot for reference.
Steps: 
------
1. Launched reported chrome 
2. Navigated the URL "http://www.espn.com/mens-college-basketball/scoreboard/_/group/2/date/20190105"
As we have observed that thumbnail images loading properly

@Reporter: Request you to retry this issue with fresh profile without any extensions & apps or reset all the flags and let us know if issue still persists.

Thanks.!

Deleted: 919297.png 302 KB

	919297.png 302 KB View Download

Fallout from background image changes, I suspect. Maybe only on Retina displays. I'll bisect.

Retried the issue on reported chrome 73.0.3662.0 using Mac 10.14.1(Retina with touch bar), 10.13.6(Retina),10.14.0 and 10.13.6. As the issue is not reproducible from our end, hence unable to provide bisect from TE end. Requesting Dev (schenney@chromium.org) to provide further inputs on it.

Thanks..!

This is specific to LayoutNG. Verified by enabling/disabling the flag in Canary. Layout team, let me know if you want me to try to fix it.

The issue is with a max-width specified on an img tag, with no max-height. The image is 70x70, the max-width is 35, and the resulting box is sized 35x70, instead of maintaining it's intrinsic dimensions and being 35x35.

This issue is marked as a release blocker with no milestone associated. Please add an appropriate milestone.

All release blocking issues should have milestones associated to it, so that the issue can tracked and the fixes can be pushed promptly.

Thanks for your time! To disable nags, add the Disable-Nags label.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

As per comment #6, able to reproduce the issue on reported chrome 73.0.3662.0 and latest chrome 73.0.3665.0 using Mac 10.14.0, Windows 10 and Ubuntu 17.10.
Steps:
1. Launched chrome 
2. Enabled LayoutNG flag by navigating chrome://flags 
3. Opened given url in comment #0 and observed that the images are stretched
Same behavior is seen from M-69(New-UI) hence considering it as non-regression and adding appropriate labels to it. Removing Needs-Bisect label to it if required feel free to add.

Thanks..! 

Out-of-flow size calculation issue.

Deleted: tc.html 354 bytes

tc.html 354 bytes View Download

ComputeReplacedSize does not take min/max-width/height into account. Need to implement overconstrained resolution from;
https://www.w3.org/TR/CSS2/visudet.html#min-max-widths

I analyzed this on Friday. As far as I could see (which I hadn't posted here yet), this isn't really related to out-of-flow positioning after all. It's just that in-flow layout lets the legacy engine calculate the size (and legacy does it correctly), while out-of-flow positioning uses NG ComputeReplacedSize(), which has issues with retaining the aspect ratio, when {min,max}-{width,height} is involved. If we switch over to always using ComputeReplacedSize(), regardless of out-of-flow or not, I suspect we'd observe the same problems for regular in-flow replaced content.

 Issue 922056  has been merged into this issue.

Friendly ping to get an update as it is marked as RBB.
Thanks..!

Fix in review: https://chromium-review.googlesource.com/c/chromium/src/+/1414872

Doesn't need to be RBB, though. LayoutNG isn't shipping in the next beta.

Issue 922276 has been merged into this issue.

The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/src.git/+/20defaa46c2c7581b85044d00dc7afa82eac6b18

commit 20defaa46c2c7581b85044d00dc7afa82eac6b18
Author: Aleks Totic <atotic@chromium.org>
Date: Tue Jan 22 21:32:18 2019

[LayoutNG] ComputeReplacedSize min/max width/height fix

This fix introduces a difference between how Legacy and
NG handle an edge case.
When replaced element:
- has no intrinsic size, has no aspect ratio,
- has border+padding.

The spec specifies that element's inline size should be computed
as stretch-width, filling the container.

Legacy violates the spec by overflowing the container by
width of border+padding.
NG implements spec behavior.

Bug:  919297 
Change-Id: I7839b94b2be86bbce30adeea6942ac5235ebacdc
Reviewed-on: https://chromium-review.googlesource.com/c/1414872
Commit-Queue: Aleks Totic <atotic@chromium.org>
Reviewed-by: Morten Stenshorne <mstensho@chromium.org>
Cr-Commit-Position: refs/heads/master@{#624928}
[modify] https://crrev.com/20defaa46c2c7581b85044d00dc7afa82eac6b18/third_party/blink/renderer/core/layout/ng/ng_length_utils.cc
[add] https://crrev.com/20defaa46c2c7581b85044d00dc7afa82eac6b18/third_party/blink/web_tests/external/wpt/css/css-position/position-absolute-replaced-minmax-expected.txt
[add] https://crrev.com/20defaa46c2c7581b85044d00dc7afa82eac6b18/third_party/blink/web_tests/external/wpt/css/css-position/position-absolute-replaced-minmax.html
[add] https://crrev.com/20defaa46c2c7581b85044d00dc7afa82eac6b18/third_party/blink/web_tests/flag-specific/enable-blink-features=LayoutNG/external/wpt/css/css-position/position-absolute-replaced-minmax-expected.txt