- Issue created by @mfb
- 🇬🇧United Kingdom catch
BigPipe uses the AJAX system for this, so it's likely that if it can't do this, it's a general bug in the AJAX system (although might be harder to reproduce/write tests without big pipe).
- 🇺🇸United States mfb San Francisco
A comment in
Drupal\bigpipe\Render\BigPipesays
If additional asset libraries or drupalSettings were attached by any of the placeholders, then we need to re-render scripts_bottom.
- seemingly forgetting that we don't necessarily know where drupalSettings lives, maybe it was in the
<head>element. Fingers crossed someone more knowledgeable about the AJAX system could figure out a good way to resolve this.. :) - 🇺🇸United States mfb San Francisco
AFAICT, the AJAX system seems to be able to merge new settings from an AJAX response into the global settings just fine, it's just not happening when BigPipe processes placeholders.
- 🇺🇸United States mfb San Francisco
@catch I did some more debugging on this and determined that this bug only affects manually created, non-markup placeholders, which are essentially skipped - although still broken - by BigPipe.
Many placeholders will not be affected by this bug because they use automatically-created placeholders ('#create_placeholder' = TRUE)