Come together with the global Drupal community in Rotterdam, 28 Sept – 1 Oct 2026. Sessions, contribution, connection, and Early Bird savings until 8 June.Since updating to 2.1.0-alpha12, the first newly added component works as expected. However, any additional components do not get the edit toolbar or the little plus signs to add additional components until the content is saved.
I believe this issue is related to this error message in the console.
dialog.element.min.js?s6aml4:374
Uncaught DOMException: Failed to execute 'define' on 'CustomElementRegistry': the name "mercury-dialog" has already been used with this registry
at /modules/contrib/mercury_editor/build/js/dialog.element.min.js?s6aml4:374:1330
at /modules/contrib/mercury_editor/build/js/dialog.element.min.js?s6aml4:374:1345
at at (/modules/contrib/mercury_editor/build/js/dialog.element.min.js?s6aml4:56:291)
at /modules/contrib/mercury_editor/build/js/dialog.element.min.js?s6aml4:374:1274
at /modules/contrib/mercury_editor/build/js/dialog.element.min.js?s6aml4:374:1484
Issue fork mercury_editor-3411056
Show commands
Start within a Git clone of the project using the version control instructions.
Or, if you do not have SSH keys set up on git.drupalcode.org:
changes
Comments
Comment #2
justin2pin commentedHi @jesss - Is this still an issue for you? Can you confirm what version of Drupal you are using (i.e. 10.1 vs 10.2)? Thanks!
Comment #5
justin2pin commentedThanks for reporting this issue. It looks like alpha13 introduced a regression for Drupal 10.1.x related to the way the ajax page state libraries value is passed during ajax requests. MR33 should fix the issue for Drupal 10.1.x and passes tests for 10.2.x.