#39073 closed defect (bug) (fixed)
Twenty Seventeen header image is compressed
Reported by: | dlh | Owned by: | davidakennedy |
---|---|---|---|
Milestone: | 4.7 | Priority: | normal |
Severity: | normal | Version: | 4.7 |
Component: | Bundled Theme | Keywords: | has-patch commit dev-reviewed |
Focuses: | Cc: |
Description
This should be replicable by visiting a post on a fresh install running Twenty Seventeen. See attached screenshot.
Attachments (5)
Change History (17)
#2
@
8 years ago
- Keywords has-patch added
Removing the positioning and transform negation in the feature query looks to fix this.
#5
@
8 years ago
@sanchothefat This was on Chrome 54.0.2840.98, macOS 10.12.1. I'm sorry, but I haven't been following Twenty Seventeen closely enough to add much more.
#6
@
8 years ago
- Keywords needs-testing added
Thanks for the report @dlh!
In 39073.2.patch, I fix the issue, which ultimately is a CSS specificity problem. I move the feature query below where it's applied in browsers that don't support feature queries or object-fit
and apply the appropriate selector for the interior pages. The problem was that the rules had the same specificity, so this way, the cascade takes over.
We still need the transforms and position changes for fallbacks in browsers that do not support object-fit
and feature queries.
#7
@
8 years ago
- Keywords needs-testing removed
@dlh no worries, me either. I'm just not able to reproduce what you're seeing there
@
8 years ago
This fixes inheritance issues with transform on header images that aren't the home/front page
#8
@
8 years ago
Tested @davidakennedy's patch in a range of browsers, works for me:
- IE 8 - 11
- Latest on Mac: Chrome, Firefox, Safari
- Latest on Windows: Chrome, Firefox
I'm happy for it to go in trunk.
Instead of putting an
<img>
inside a<div>
, what if we made the image a background to the<div>
with user-defined options available for the alignment (with defaultcenter center
)? Or is there a specific reason we are doing the<img>
inside the<div>
(such as being able to replace<img>
with<video>
when it's a video background)?