Make WordPress Core

Changes between Initial Version and Version 1 of Ticket #59432, comment 6


Ignore:
Timestamp:
11/06/2023 07:59:59 AM (4 months ago)
Author:
bedas
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #59432, comment 6

    initial v1  
    333. It appears to me that adding HTML5 themes support for scripts and styles does indeed remove the `type`. Good, but it does not remove the `/>` for the link tag, like when enqueueing styles (but there are countless others). We can see an example of this hardcoded `/>` in `"<link rel='%s' id='%s-css'%s href='%s'%s media='%s' />\n"`,in `WP_Styles->do_item()`. So the statement that a theme has to declare said support and it will solve everything is only half-applicable.
    44
    5 Of course WP is free to choose what is best, but it should also respect the choice of the webmaster, which, presuming we allow the HTML5 support, should of course also be applied to these "warnings". Adding support does not just mean avoiding errors.
     5Of course WP is free to choose what is best, but it should also respect the choice of the webmaster, which, presuming we allow the HTML5 support, should of course also be applied to these "warnings" or "information"s. Adding support does ''not'' just mean avoiding errors.
    66
    77I would suggest that: