🐛 Use the default theme when rendering content blocks Fixed Introduced a Theme Negotiator to render Content Blocks using the Active theme in the editor. Unfortunately, it turns out that that that also inadvertently updates the main page's ajax_page_state.theme value to the active theme, resulting in future AJAX requests to other routes potentially using the wrong theme (e.g. the media library ajax route). This happens because the all AJAX responses include the ajax_page_state.theme as a drupalSetting which gets merged back into the main page settings.
Since we're only using the Theme Negotiator on the one route, I suggest we ditch the negotiator and just do a little switcheroo on the theme before rendering the block content, then switch the active theme back to avoid messing with the main page's ajax page state.
MR incoming!
Fixed
3.0
Code
Automatically closed - issue fixed for 2 weeks with no activity.