[wp-trac] [WordPress Trac] #64015: Reconsider removal of import map polyfill

[WordPress Trac]

#64015: Reconsider removal of import map polyfill
---------------------------+-------------------------
 Reporter:  joedolson      |       Owner:  (none)
     Type:  defect (bug)   |      Status:  new
 Priority:  normal         |   Milestone:  7.0
Component:  Script Loader  |     Version:  6.5
 Severity:  normal         |  Resolution:
 Keywords:                 |     Focuses:  javascript
---------------------------+-------------------------
Changes (by joedolson):

 * milestone:  Awaiting Review => 7.0


Comment:

 I'm adding this issue to 7.0 to be resolved. In my opinion, the number of
 issues opened that are a direct consequence of removing the importmap
 polyfill is a clear indication that it may have been premature, but I also
 appreciate that maintaining eternal support for clearly obsolete devices
 is a challenge.

 I'm not sure we have actual documentation about specific policies; but we
 have a history of choosing to remove things in the admin before removing
 them in themes. E.g. in #54421 we delayed the removal of the skip link
 polyfills for a couple years for extended support.

 I think what we really need is to become more explicit about how we
 differentiate between front-end and back-end support. There is a
 difference, because support for the front end has a vastly broader
 footprint than the back end.

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