Scenario
As a course author using the new React-based Unit editor, when I add an advanced XBlock which uses children and click View ->, I am brought to a page which shows its children.
Expected
From the View -> page, I can view, edit, and delete existing child components and add new child components. Here is what that looks like in the legacy unit editor:
Actual
From the View -> page, I can view, edit, and delete existing child components, but there is no option to add child components.
Testing notes
This affects blocks which use the children-editing interface provided by core Studio and/or the xblock-utils library. We have confirmed it affects:
And we suspect it affects:
These blocks are not affected:
- library_content -- this block has it own special UI for picking a legacy lib
- itembank -- this block has its own special UI for selecting children from V2 libs
- split_test (built-in) -- the children of the split_test are units, and it seems that those unit editors are working fine w.r.t. adding children
- randomize -- adding children never worked on this one
Scenario
As a course author using the new React-based Unit editor, when I add an advanced XBlock which uses children and click
View ->, I am brought to a page which shows its children.Expected
From the
View ->page, I can view, edit, and delete existing child components and add new child components. Here is what that looks like in the legacy unit editor:Actual
From the
View ->page, I can view, edit, and delete existing child components, but there is no option to add child components.Testing notes
This affects blocks which use the children-editing interface provided by core Studio and/or the xblock-utils library. We have confirmed it affects:
And we suspect it affects:
These blocks are not affected: