Join GitHub today
GitHub is home to over 50 million developers working together to host and review code, manage projects, and build software together.
Sign upLayout should more carefully determine image intrinsic width/height #79
Comments
|
If this is really about intrinsic dimensions, then CSS width and height do not affect those. Nor do HTML width/height attributes. The only thing that affects them is the image data. When there is no image data, there is typically no image box (with some exceptions for "during the loading process" and "in quirks mode", for which you can use somewhat arbitrary intrinsic dimensions). |
ChrisParis
pushed a commit
to ChrisParis/servo
that referenced
this issue
Sep 7, 2014
Tests for the progress element, from Dan Smith of TestTWF Seattle 2013.
glennw
added a commit
to glennw/servo
that referenced
this issue
Jan 16, 2017
Implement better scan and split strategies for the atlas allocator, and use as large of a texture as the hardware allows.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
In
Box::get_min_width(), the layout engine currently just uses the decoded image width/height. But, if the image couldn't be loaded, isn't finished loading, has CSS 'width' or 'height', borders, margins, or Node attributes width=, height= set, its dimensions may be different.