openedx / openedx/frontend-app-authoring

Generally glitchiness with duplicating components in a unit

Open
#2,500 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
TypeScript
Stars
17
Forks
218
Avg merge
9d 20h
Merged PRs (30d)
20

Description

For background context: in this issue, I've outlined the glitchy behavior we're seeing when duplicating children of a container block:

While trying to determine the "expected" behavior for the above, I encountered a variety of weird behavior while trying to duplicate blocks just in the normal Unit editor, including:

  • Popover editor not loading for problem editor:
    Image
  • Popover editor did load when I tried it on another problem, but it scrolled to the wrong spot on the page
  • Conditional block did not shows up as duplicated until I refreshed the page

I'm not sure whether there is 1 underlying issue or multiple, or how much of this is specific to my development environment, but I think we generally need some QA around duplication in some matrix of all the following scenarios:

  • In a short unit
  • In a long unit, where we'd expect the page to be scrolled to to the right place
  • Within a short and a long container (once that bug is resolved)
  • For a block with a pop-over editor (html/problem/video/itembank)
  • For a block with a custom editor (drag-and-drop, ora, lti)
  • For a block with children (split_test)

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reproducing duplication in the Unit editor across the scenarios listed, including short and long units, popover and custom editors, and blocks with children. Compare findings with the linked issue 2499; done means the duplication behavior is characterized across the matrix and each glitch is isolated to a clear follow-up or fix.

Written by the indexing model from the issue text.

Assessment

Tech stack
react, typescript
Domain
frontend, testing-qa
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.