LivelyKernel / LivelyKernel/lively.next

Padding in nested tiling layouts screws up fill behavior

Open
#1,623 0 comments 0 reactions 0 assignees View on GitHub
:lady_beetle: bug
Dominant language
JavaScript
Stars
90
Forks
20
PR merge metrics
No merged PRs in 30d

Description

**Describe the bug**
When nesting morphs via tiling layouts, the presence of a padding on one of the laid out morphs can mess up the sizing behavior when such a morph is set to fill its parent. In those cases the morph no longer assumes the proportional space allotted but instead claims the proportional space while also consuming the space of the padding. This leads to uneven fill behavior, where for instance two morph in a row where each should fill their parent will now longer each receive 1/3 of the free space but instead the one with the padding will take up more space then the allowed 1/3.
**Setup**
- macOS

**Version**: a6de985aed8a633a138fef1c32bbd2c36ac1f5d4

Contributor guide

Open the contributing guide

Research direction

No file, test, or entry point is named. Reproduce the nested tiling layout on macOS using the reported version, then trace how padding and fill sizing are calculated; done means equally filling morphs retain their proportional allocation when one has padding.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript
Domain
frontend
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.