โšก๏ธ Live updates comments, jobs, and issues, tagged with #JavaScript will update issues and activities on this page.

Issues

The last 100 updated issues.

Activities

The last 7 days of comments and CI jobs.

  • ๐Ÿ‡จ๐Ÿ‡ฆCanada Ambient.Impact Toronto

    Looks like my changes in the issue fork have some grouping problems with Drupal 10.1+'s aggregation system in that it seems to result in aggregates sometimes being generated without a file included on one page and then again with all the same contents plus the additional file. This has been biting us in ๐Ÿ› Turbo: JS aggregation causes the RefreshLess JavaScript to evaluate more and more times on navigation Active where we're trying to get Hotwire Turbo working with JS aggregation on but it's downloading and evaluating (nearly) the same JavaScript, and after a bunch of debugging, I finally realized it was due to us using the defer attribute plus this issue fork, because removing the attribute and removing the patch instantly fixed the JS aggregates.

    On top of that, given that there are also other attributes that we may want to group by (e.g. fetchpriority as mentioned by #81) and that new attributes may come along later, I propose reworking this as a more generic approach:

    Instead of hard-coding the attributes (i.e. async, defer, etc.) we add a settings.php setting which is an array of attribute names that can be grouped, with the default being ['async', 'defer'] - this will make it easy for sites to opt into aggregating with other attributes based on their needs and be more future proof.

  • ๐Ÿ‡ซ๐Ÿ‡ทFrance fgm Paris, France

    For anyone curious about the Drupal parts in the talk above, the segment mentioning Drupal (and WP) starts at 21:00.

  • ๐Ÿ‡บ๐Ÿ‡ธUnited States FatherShawn New York

    It seems to me that what is new in HTMX is expressing and documenting the actions in the HTML. By expanding the hypermedia controls using attributes and including all the HTTP verbs in those controls it completes HTTP/HTML to be a fully expressive hypermedia system.

    I've done some creative things in custom projects in the past with our AJAX system, but much of that was not evident by looking at the markup. I haven't built anything yet with HTMX, having just encountered it via this issue, but I'm really looking forward to taking it for a spin!

  • ๐Ÿ‡บ๐Ÿ‡ธUnited States effulgentsia

    Yes, there's not much conceptually new in HTMX that we didn't have in Drupal 6's AHAH which then became Drupal 7's AJAX. But the HTMX community did a really nice job in creating a more refined API and documenting it well.

  • ๐Ÿ‡ฆ๐Ÿ‡บAustralia larowlan ๐Ÿ‡ฆ๐Ÿ‡บ๐Ÿ.au GMT+10

    Interesting that in this PHP UK session he points out HTMX is something we've already had in Drupal https://youtu.be/Yb4mDfwOUXE

  • ๐Ÿ‡ณ๐Ÿ‡ฟNew Zealand quietone New Zealand

    I'm triaging RTBC issues โ†’ . I read the IS and the comments. I didn't find any unanswered questions.

    This is failing commit-code-checks, specifically spelling. Setting back to Needs work.

  • ๐Ÿ‡บ๐Ÿ‡ธUnited States cosmicdreams Minneapolis/St. Paul

    I agree with the contrib approach. HTMX needs to be able to demonstrate that in cases where it can impact pieces within core that it can be a "drop ship" replacement of those pieces.

    If I could have a magic wand and get everything I want, Core wouldn't use any 3rd party javascript libraries (and still be awesome). Some days it feels like that reality is achievable but others it seems foolish.

    That said, HTMX's value appears to be in interactivity. So when thinking about the intersection of core and HTMX the areas that have a lot of user interactivity, places like Views, Content Administration, and Recent log messages. Other parts that feel way too ambitious like Layout Manager and impacting ajax.js itself are things that may one day be on the table, but yea, whew sounds like a lot of dramatic change.

    And it should be said that HTMX isn't the "end of the line" / final form of the ideas that it advances. I'm concerned that if we would invest a ton of effort adopting this library in core that we would have to redo / undo some of that work in the near term.

    Going forward

    Where should we meet to collaborate on ideas?

  • ๐Ÿ‡ฉ๐Ÿ‡ชGermany Anybody Porta Westfalica

    Thanks for all the feedback here. I think all makes sense. Introducing HTMX in Drupal is not a simple task and will require many resources.
    So starting in contrib, making concepts and keep an eye on the general adoption of HTMX is surely the right way to go. Especially we should have a look at DX improvements. I agree that the current AJAX system in Drupal works, but for me it always has been and still is kind of (wonderful) magic in many parts. I agree with @catch in #17 and saw many developers struggling with it. It's not really straight forward, but that doesn't mean it's not good!

    So I think we're at a point, where things work well, but it doesn't mean it couldn't get better. Especially for developers new to Drupal it might be a simplification and unification, similar to what happened with Symfony in Drupal 8 in contrast to the custom codebase in Drupal 7, that also worked great, but was a good choice to use a standard library to make the switch to Drupal easier.

    So there are many good reasons for and against HTMX and the decision has to be made wisely. Trying it out in contrib is a good next step and perhaps someone would like to research the general pro's and con's and feedback for HTMX?

  • ๐Ÿ‡ฌ๐Ÿ‡งUnited Kingdom AaronMcHale Edinburgh, Scotland

    Can we get a use-case/list of pain points with the current setup

    I hit up against this issue back in 2018 and it's still a problem today, required a hacky workaround ๐Ÿ› Ajax is broken in forms built within an Ajax callback Active .

    Still a problem 6 years later. (Also was 2018 really 6 years ago?! Oh my...)

    I think that illustrates why we may benefit from replacing our custom AJAX solution with a solution well supported by the wider community.

Production build https://api.contrib.social 0.61.6-2-g546bc20