Make WordPress Core

Changes between Version 1 and Version 2 of Ticket #53070, comment 5


Ignore:
Timestamp:
04/28/2021 09:31:43 PM (4 years ago)
Author:
johnjamesjacoby
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #53070, comment 5

    v1 v2  
    2121It used to work a lot like this, but over time everything drifted apart and got commingled together a few times. Add into that, the modern desire to slim the CSS down with JavaScript, is in conflict with the convenience of having everything partitioned and readily available and enqueued via PHP.
    2222
    23 As a PHP developer, I want to announce to WordPress the core CSS my plugin needs loaded, and that's it. I'm contradicting myself here, but if I can't do that or if the reliability of that is diminished, what will happen is plugins will all start rolling everything out on their own, and there simply will no longer be a "native looking WordPress plugin" because the core CSS cannot be trusted to do its job.
     23As a PHP developer, I want to announce to WordPress the core CSS my plugin needs loaded, and that's it. I'm contradicting myself here, but if I can't do that or if the reliability of that is diminished, what will happen is plugins will all start rolling everything out on their own, and there simply will no longer be a "native looking WordPress plugin" because the core CSS cannot be trusted to do its job. (Many plugins are already going this route, and I think it's ultimately a worse experience for everyone - more work, more to learn, more confused users, less familiar UI everywhere.)