New issue
Advanced search Search tips

Issue 810370 link

Starred by 1 user

Issue metadata

Status: Fixed
Owner:
Closed: Oct 26
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 3
Type: Bug



Sign in to add a comment

[LayoutNG] Intrinsic size calculation too "correct"

Project Member Reported by mstensho@chromium.org, Feb 8 2018

Issue description

I'm about to file a CL for intrinsic size calculation, which will deal more correctly with floats. However, this is going to make us "better" at it than the others (Edge, Firefox, Blink legacy).

<div id="stf" style="position:absolute;">
  <div id="f1" style="float:left; width:10px; height:10px;"></div>
  <div id="wrapper">
    <div id="f2" style="float:left; width:10px; height:10px;"></div>
  </div>
</div>

#f1 and #f2 get stacked vertically in Edge, Firefox and Blink legacy.
Without #wrapper, they are all able to place #f1 and #f2 beside each other, though.

I'm pretty sure slightly older versions of Internet Explorer (like IE10) were able to pass such a test, but I suspect that they had to  "dumb down" the intrinsic width calculation machinery to match the others.
 
tc.html
358 bytes View Download
Cc: mstensho@chromium.org
Our rendering is identical with Edge and FF, what's the next step here Morten?
Owner: ikilpatrick@chromium.org
Status: Fixed (was: Available)
Fixed by ikilpatrick, and I even reviewed it.

https://chromium-review.googlesource.com/c/chromium/src/+/1125582#message-8184b4a6ba5b841dd385c92d90a13bb4e280bf32

As eae points out, we're now identical to the others, and we're not too "correct" anymore.

Sign in to add a comment