DEP 84: Rejuvenate form media #84
Conversation
There was a problem hiding this comment.
I think introducing the JS class from django-js-asset into Django would be worthwile; probably a few parts of the admin should be refactored to take advantage of this? It's very stable, nothing has changed since the beginning of 2022.
| - ES modules | ||
| - Import maps | ||
| - Dynamic module imports | ||
| - async, defer scripts | ||
| - CSPs via nonce attributes | ||
| - integrity attribute | ||
| - fetchpriority attribute | ||
| - nomodule attribute | ||
| - Arbitrary script attributes | ||
| - Preloading / speculative loading | ||
| - Resource ordering (see `capo.js <https://rviscomi.github.io/capo.js/>`_) | ||
| - Web Components |
There was a problem hiding this comment.
I think that's a very complete list. As I already said on the forum thread, I think that the frontend tooling space is still moving so quickly that it's hard to know which tools may or may not be useful in a few years time. When I think about Django and it's stability I have a horizon of several years always, with frontend tooling that's just not the case. If we had more fellows and/or more people which are paid to work on Django it could be a good idea. Even though I'm actually a (p)react and web/rspack fan I think it's a good idea for Django to stay in the backend world.
So, I think there's a lot of value in trying to support CSP (that was one of the motivations for django-js-asset, see https://406.ch/writing/django-admin-apps-and-content-security-policy-compliance/ ), supporting additional arbitrary attributes on <script> tags etc. but that's it.
I'm not sure I understand the resource ordering thing. Django already supports relatively complex dependencies (at least since https://code.djangoproject.com/ticket/30153). Of course that doesn't do anything about the initial page loading performance, but then you're already in the area of bundlers again.
There was a problem hiding this comment.
From my perspective everything on that list has already proven its usefulness quite clearly! Additional attributes on <script> would be really useful but that feels to me like a rejuvenation of the Media API to bring it to 2014 standards rather than 2024.
There was a problem hiding this comment.
Should we also be adding anything about Django providing polyfills?
As in
Opt in set of polyfills to support some/all of the above via pre-approved CDNs. Import maps, ESM, Web Components being the main ones.
This is something the Rails approach did I believe, to allow for a 'simple' cross browser support approach where developers didn't have to think about what to include.
Big +1. When I pushed for django/django@4c76ffc2d6c77, it was my hope that at some point we could agree on some class-based JS/CSS objects (see the example in test_media.py). |
|
Is there anything I can do to move this forward? |
|
@matthiask would you be up for writing the "new attributes for |
Draft, not ready for review yet
Read the DEP as HTML
For context, see the forum thread: Rejuvenating vs deprecating Form.Media.