[wp-trac] [WordPress Trac] #46044: Add `wp_get_update_php_annotation()` to return the Update PHP annotation

[WordPress Trac]

#46044: Add `wp_get_update_php_annotation()` to return the Update PHP annotation
-----------------------------------------------+---------------------
 Reporter:  afragen                            |       Owner:  (none)
     Type:  defect (bug)                       |      Status:  new
 Priority:  normal                             |   Milestone:  5.2
Component:  Plugins                            |     Version:  trunk
 Severity:  normal                             |  Resolution:
 Keywords:  has-patch servehappy dev-feedback  |     Focuses:
-----------------------------------------------+---------------------

Comment (by flixos90):

 @aaroncampbell @afragen
 I think `<br><span>...</span>` is very specific to where the content needs
 to occur, just as much as `<p>...</p>` is very specific to where the
 content needs to occur. One variant is semantically correct in one
 context, the other one is semantically correct in another. I don't think
 there is a foundation to argue about one or the other being more
 applicable generally - forcing ''any'' wrapping markup here will get us
 into trouble with semantics one way or the other, so I think support for
 `$before` and `$after` is necessary.

 `<p class="description">` and `</p>` must be the defaults only because
 they are what is used right now. Not because they fit better than
 `<br><span class="description>` and `</span>` - again, no variant works
 better than another variant IMO because it all depends on the context.

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