[wp-trac] [WordPress Trac] #62731: Inline CSS inserted by wp_print_auto_sizes_contain_css_fix too high in HTML

[WordPress Trac]

#62731: Inline CSS inserted by wp_print_auto_sizes_contain_css_fix too high in HTML
---------------------------------------------------+---------------------
 Reporter:  superpoincare                          |       Owner:  (none)
     Type:  enhancement                            |      Status:  new
 Priority:  normal                                 |   Milestone:  6.9
Component:  Media                                  |     Version:  6.7.1
 Severity:  minor                                  |  Resolution:
 Keywords:  has-patch needs-testing has-test-info  |     Focuses:
---------------------------------------------------+---------------------
Changes (by SirLouen):

 * keywords:  has-patch => has-patch needs-testing has-test-info


Comment:

 For testers of this patch, the same tests apply, as in #62413

 Replying to [comment:5 westonruter]:
 > It seems like it should have been enqueued as an inline style like was
 done in #58775 for the emoji styles. I've opened a
 [https://github.com/WordPress/wordpress-develop/pull/8954 PR] to make this
 change. It's currently a draft because I'd like to add tests before
 proceeding to commit, and I want affirmation on the direction before
 writing tests.

 Doesn't make sense to me, deprecating such nouveau function
 `wp_print_auto_sizes_contain_css_fix`. I understand this the backwards
 compatibility policy, but we can be pretty confident noone is using this
 (and if they were using it, they might have reported this).
 [https://wpdirectory.net/search/01JXE4QAMTK4XGK3MZVYMW9A1D So just wipe
 it].


 Replying to [comment:3 sabernhardt]:
 > If the //title// should be earlier, block themes probably could add
 'title-tag' support now instead of using the
 `_block_template_render_title_tag` function. (@westonruter proposed the
 [https://github.com/WordPress/gutenberg/pull/17626/files#r329165034
 separate function], in the context of the Gutenberg plugin, and #53176
 carried it over with a new name.)

 Doesn't this seem to be a separate topic for a ticket?

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/62731#comment:6>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform