#3588 closed enhancement (wontfix)
custom header image repeats on y-axis
Reported by: | DJPaul | Owned by: | |
---|---|---|---|
Milestone: | Priority: | normal | |
Severity: | normal | Version: | 1.5 |
Component: | Templates | Keywords: | |
Cc: |
Description
Uploading a custom header with the size of 1250x125px (as recommend on Appearance > Header) repeats on the y-axis. Actual height of header appears to be 133px.
Attachments (1)
Change History (14)
#2
@
13 years ago
Yep. Height of header seems very arbitrary when you take into account browser zooms, etc. Could set background-repeat to no-repeat for the y-axis, but that looks a bit strange because it doesn't appear the image reaches the bottom of the main nav block… plus someone may be using that creatively.
#4
@
13 years ago
- Keywords has-patch added
- Version set to 1.5
This is to do with the margins on #header #nav
and #header #search-bar
.
Tested this in v1.2.x and this issue specific to 1.5 only, so I'd rather revert [5155] and remove the extra 7px of margins. See 01.patch.
#6
@
13 years ago
- Milestone changed from 1.5 to 1.5.1
- Type changed from defect to enhancement
Not for 1.5; no time to judge what the impact would be on any other templates within BP-Default. We can review this for a future release.
#7
@
13 years ago
I'd make an argument that we should consider this issue for v1.5.0 because v1.5.0 hasn't been released yet.
If we release v1.5 as-is, you'd be telling users that 1250x133 is acceptable (133 is an odd number). Also, previous child themes that inherit v1.5 CSS will get this extra margin.
There shouldn't be any impact as far as templates are concerned.
#8
@
13 years ago
Having just developed my own solution before performing a search (to find this trac) my vote is for:
div#header { background-repeat: no-repeat; }
without this the repeated header image looked really horrible on narrow displays.
#10
@
13 years ago
- Milestone changed from 1.6 to Future Release
I think it's too late to tinker with this. Themes might already be working around it, and anything we do is going to noop something for someone. Punting to Future Release unless there's a compelling argument + a patch.
Seems better to change the recommendation to match the CSS, right?