Come together with the global Drupal community in Rotterdam, 28 Sept – 1 Oct 2026. Sessions, contribution, connection, and Early Bird savings until 8 June.Overview
In #3472299: Update default config to make a fresh install result in an XB UI with an empty canvas we made it so that anybody you creates an article an then uses XB at xb/node/1 will start with an empty canvas
To limit the scope of the issue we used the same defaults that we had before 3472299 in XBTestSetup to create the node that E2E tests use. Therefore the E2E tests all start with a pre-filled canvas
Since we already found and solved a problem in #3472299-20: Update default config to make a fresh install result in an XB UI with an empty canvas(linked to explanation) that only happened on when the canvas was empty, is possible we could introduce new problems that only show up canvas is empty and we have no test coverage for this situation
Proposed resolution
Create at least 1 E2E test that starts with an empty canvas and then places 1 component on the canvas.
User interface changes
Issue fork experience_builder-3474257
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
tedbowWill let the front end folks determine the priority. Though the problem with an empty canvas discovered in #3472299-20: Update default config to make a fresh install result in an XB UI with an empty canvas was actually a backend issue.
Comment #3
wim leersComment #4
wim leersBumping to because without it, our E2E tests do not cover the full spectrum of typical use.
Plus, it already slowed velocity down once before — even though the root cause was a simple back-end fix.
Comment #5
tedbowHit us again #3485937-10: Drag and drop in the preview not working correctly
Comment #8
bnjmnmComment #9
hooroomooComment #11
hooroomoo