Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

[Bug] Competency Management page: columns need a fixed height, and competency rows don't show a clickable cursor

Open
  • Is something wrong?
#835 0 comments 0 reactions 1 assignee View on GitHub

Maintainers usually reply within 1 day

@AShatsila is already working on this.

Since Sep 26, 2026.

Assessment

This issue has not been assessed yet.

Description

Environment: Master Sandbox, https://apps.master.openedx.io/authoring/taxonomy/46/competencies

Select any competency before checking the points below, so that the right-hand course panel is shown.

  1. The left column (competency tree) is shorter than the right column (course panel). Both columns should have the same height.
Image
  1. When all competencies are expanded with "Expand All", the left column grows far below the right column, and a large empty area appears under the course panel. On desktop, both columns should have the same fixed height, and the competency tree should scroll inside the left column instead of making the page taller.
Image
  1. The course panel shrinks when the results contain fewer courses, for example after searching "EDL", and the content below it moves up the page. On desktop, the course panel should keep a fixed height, so the page layout doesn't jump when results change. That height should fit 10 courses, which is one full page of results, even when fewer courses are returned.
Image
  1. The mouse cursor doesn't show that a competency row is clickable. Clicking a row selects the competency, but over the row label the cursor is a text cursor instead of a pointer. Every selectable competency row should show a pointer cursor over its whole area.
Image

On small screens, where the two columns stack vertically, the current layout works as intended. Points 1 to 3 apply to the desktop layout only.

Dominant language
Python
Stars
10
Forks
33
Avg merge
2d 4h
Merged PRs (30d)
10

Getting set up

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.

More from openedx/openedx-core

All issues in openedx/openedx-core

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.