Welcome to Software Development on Codidact!
Will you help us build our independent community of developers helping developers? We're small and trying to grow. We welcome questions about all aspects of software development, from design to code to QA and more. Got questions? Got answers? Got code you'd like someone to review? Please join us.
Post History
#3: I still don't know what exactly is going on, but experimenting today, I found a workaround at least: align-items: normal; on the container and object-fit: scale-down; on the image. Due to the...
Answer
#2: Post edited
by
martixy
·
2024-04-10T15:45:54Z (7 months ago)
- **#3:** I still don't know what exactly is going on, but experimenting today, I found a workaround at least:
- `align-items: normal;` on the container and `object-fit: scale-down;` on the image.
- **#1:**
Due to the way object-fit works, it circumvents the problem on chrome. But it does highlight another inconsistency. The description of `scale-down` is:- _Size the content as if none or contain were specified, whichever would result in a smaller concrete object size._
- This statement is lifted directly from the spec, but it is not true on chrome, providing another hint that it is indeed a bug! `none` behaves differently than `scale-down` on chrome! [Example](https://www.deviantart.com/roen911/art/Hauler-Brengun-Dewoitine-D-520-1038627154) - though demonstrating the problem will depend on the resolution of your screen.
- **#3:** I still don't know what exactly is going on, but experimenting today, I found a workaround at least:
- `align-items: normal;` on the container and `object-fit: scale-down;` on the image.
- Due to the way object-fit works, it circumvents the problem on chrome.
- **#1:**
- But this does highlight another inconsistency. The description of `scale-down` is:
- _Size the content as if none or contain were specified, whichever would result in a smaller concrete object size._
- This statement is lifted directly from the spec, but it is not true on chrome, providing another hint that it is indeed a bug! `none` behaves differently than `scale-down` on chrome! [Example](https://www.deviantart.com/roen911/art/Hauler-Brengun-Dewoitine-D-520-1038627154) - though demonstrating the problem will depend on the resolution of your screen.
#1: Initial revision
by
martixy
·
2024-04-10T15:45:05Z (7 months ago)
**#3:** I still don't know what exactly is going on, but experimenting today, I found a workaround at least: `align-items: normal;` on the container and `object-fit: scale-down;` on the image. **#1:** Due to the way object-fit works, it circumvents the problem on chrome. But it does highlight another inconsistency. The description of `scale-down` is: _Size the content as if none or contain were specified, whichever would result in a smaller concrete object size._ This statement is lifted directly from the spec, but it is not true on chrome, providing another hint that it is indeed a bug! `none` behaves differently than `scale-down` on chrome! [Example](https://www.deviantart.com/roen911/art/Hauler-Brengun-Dewoitine-D-520-1038627154) - though demonstrating the problem will depend on the resolution of your screen.