#58675 closed enhancement (fixed)
Theme: use the_header_image_tag in core themes
Reported by: |
|
Owned by: |
|
---|---|---|---|
Milestone: | 6.4 | Priority: | normal |
Severity: | normal | Version: | 4.4 |
Component: | Bundled Theme | Keywords: | has-patch commit |
Focuses: | performance | Cc: |
Description (last modified by )
There are a number of core themes that do not use the the_header_image_tag
function. This function was added in WP 4.4 after some of these theme were introduced. Add a backwards compatibility shim to use this function in core themes.
See the following core themes that need to be updated.
Twenty Eleven
Twenty Fourteen
Twenty sixteen
Twenty Ten
Twenty Twelve
Change History (20)
This ticket was mentioned in PR #4760 on WordPress/wordpress-develop by @spacedmonkey.
3 months ago
#1
- Keywords has-patch added
#2
@
3 months ago
- Summary changed from Use the_header_image_tag in 2016 theme to Twenty Sixteen: use the_header_image_tag
#3
@
3 months ago
- Description modified (diff)
- Focuses performance added
- Milestone changed from Future Release to 6.3
- Summary changed from Twenty Sixteen: use the_header_image_tag to Theme: use the_header_image_tag
This ticket was mentioned in PR #4797 on WordPress/wordpress-develop by @spacedmonkey.
3 months ago
#4
Trac ticket: https://core.trac.wordpress.org/ticket/58675
#5
@
3 months ago
- Summary changed from Theme: use the_header_image_tag to Theme: use the_header_image_tag in core themes
#7
@
3 months ago
+1 to what @swissspidy says, while this relates to #58680, this is a broader change and goes beyond what I'd consider a critical bug fix - also relates to the fact that this bug was not introduced in trunk
but WP 4.4, so not critical.
Given that it touches the core themes with several lines of code changes. I don't feel comfortable committing this so late in the cycle, and furthermore I don't think it's critical enough. I think we should milestone this for 6.4.
cc @desrosj in case you have some guidance when to make such changes
#8
@
3 months ago
- Keywords early added
- Milestone changed from 6.3 to 6.4
- Type changed from defect (bug) to enhancement
Punting to WordPress 6.4. I agree that that this is an enhancement over a bug. I have pushed @flixos90 to add this ticket to the dev note. Header image not working with this new functionality ( and even older functionality like async decoding ), might be a little confusing. The dev note should include instructions on how to retrofit your theme to support these features and use this ticket / PR as an example.
Marking this as early, myself as the owner and changing to WP 6.4.
Keeping this as part of the performance focus, as adding source sets, decoding async and fetch priority to header images, is a performance win.
#10
@
7 weeks ago
- Keywords early removed
I don't think this scope of work must be bound to only the early
phase of the 6.4 alpha cycle, meaning if it doesn't get done during this early phase then it gets punted. Work here can happen at anytime during Alpha, i.e up to the Beta 1.
This ticket was mentioned in Slack in #core-performance by spacedmonkey. View the logs.
4 weeks ago
This ticket was mentioned in Slack in #core-performance by spacedmonkey. View the logs.
4 weeks ago
@spacedmonkey commented on PR #4797:
3 weeks ago
#16
@felixarntz Go catches. Feedback actioned!
Trac ticket: https://core.trac.wordpress.org/ticket/58675