balsaPixel bug: the chart key pushes the 2D/3D trade-off chart off the full-screen view

Open
#235 2 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
Half a day
Newbie friendliness
62/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Active
Tech stack
html, javascript
Domain
design, frontend

Research direction

Start at the Trade-off 2D and 3D chart views and the chart key window layout. Reproduce the issue at 1280 × 720, 1440 × 900, and 1920 × 1080 with the key closed, open, and grouped into 8 or more groups. Done when both charts fill the screen and opening, closing, resizing, or grouping the key does not move the plot.

Written by the indexing model from the issue text.

Description

bug P2 role: dev-lead status: ready ui
Details

Bug, balsaPixel preview: the chart key (legend) window pushes the 2D and 3D trade-off charts off the full-screen display. The chart should fill the screen with the key floating over it, like every other window.

Reported by Brian, 2026-10-28. UI didn't reproduce it at 1440 × 900 in headless Chromium: the chart filled the screen under the key. It probably depends on window size or on the key's state (open, wide, after a "Group by").

Steps (Brian): open the balsaPixel preview → Analysis → Trade-off 2D (then 3D) with the Chart key open. The chart is pushed and partly off screen.

Expected:

  • The chart canvas always fills the stage.
  • Windows float over it and never change its size.
  • Opening, closing or resizing the key doesn't move the plot.
Acceptance check

At 1280 × 720, 1440 × 900 and 1920 × 1080, with the key closed, open, and grouped into 8 or more groups, the 2D and 3D chart fill the screen and the plot doesn't move when the key changes.

Notes

Brian, please add the window size and a screenshot if you can (Drive [89] Bug Documentation).


Generated by Claude Code

Dominant language
HTML
Stars
0
Forks
1
Avg merge
4h 10m
Merged PRs (30d)
99

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 briangwalker/TrussExplorer

All issues in briangwalker/TrussExplorer

Similar issues

More Design issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.