LivelyKernel / LivelyKernel/lively.next
Tooling should prevent hugging Text from having text-wrap enabled
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 90
- Forks
- 20
- PR merge metrics
- No merged PRs in 30d
Description
It is quite easy to create textmorphs which have hugging (width) enabled and also try to break their content. The "dragged" default morph from the topbar has wrapping enabled, so just enabling hugging leads to such situations. However, those lead to weird looks and make editing quite painful:
https://github.com/LivelyKernel/lively.next/assets/14252419/155ec42c-1243-43ef-992c-97976aa91b69
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by tracing the tooling that creates the dragged default morph from the topbar and the text morph behavior connecting hugging width with text wrapping. Reproduce the issue by enabling hugging on a wrapping textmorph; done when that combination no longer produces the described layout and editing problems.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- frontend, tooling
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100