Don't limit the document width, or add 'unlimited' option for width
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 50/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- typescript
- Domain
- frontend
Research direction
The payload names only the Annotate view and an existing settings=wide option that caps document width at about 1280px. Start by finding where that width cap and the wide setting are defined in the TypeScript frontend, and check how the Annotate view applies them to the document. Done when a user can let the document fill the full window width, either by default or through a new unlimited option, while the current default layout stays the same. The issue does not say whether to remove the cap or add an option, so confirm that with a maintainer first.
Written by the indexing model from the issue text.
Description
What happened?
I have 4k screen and the document I'm reviewing has really wide tables.
Instead of limiting the width with 1280px, let document fill the whole width so I don't scroll it horizontally. That would be really useful. Currently it uses only center half of my screen (with settings=wide), increasing a font make it looking really weird.
Plannotator version
v0.28.45
OS
macOS
Agent
Claude Code
Where did it happen?
Annotate
- Dominant language
- TypeScript
- Stars
- 8.7k
- Forks
- 649
- Avg merge
- 8h 35m
- Merged PRs (30d)
- 714
Getting set up
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.
More from backnotprop/plannotator
-
Pi extension on Oh My Pi: review feedback goes to an in-process subagentPossibly taken A pull request linked to this issue is open or already merged. Open
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
backnotprop/plannotator#2554 ·
Maintainers usually reply within 1 day
-
Pi extension: a gated review from the plannotator tool ends 30 s after its tab closesPossibly taken A pull request linked to this issue is open or already merged. Open
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
backnotprop/plannotator#2553 ·
Maintainers usually reply within 1 day
-
Enhancement: Make explainers printablePossibly taken A pull request linked to this issue is open or already merged. Open
Difficulty 2/5 1-3 hours Newbie friendliness 67/100
backnotprop/plannotator#2317 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
backnotprop/plannotator#2290 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
backnotprop/plannotator#2243 · 2 comments · 2 reactions ·
Maintainers usually reply within 1 day
All issues in backnotprop/plannotator
Similar issues
-
test: claim-conflict drop leaves both facts active and is never re-proposed (untested review cell)Open
Difficulty 2/5 1-3 hours Newbie friendliness 83/100
Maintainers usually reply within 1 day
-
[Feature]: Usage page should show API-equivalent cost and say when a connected plan shows info onlyOpenenhancement from-x
Difficulty 2/5 1-3 hours Newbie friendliness 66/100
nightly-labs/openbot#4867 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
egonSchiele/agency-lang#1377 ·
Maintainers usually reply within 1 day
-
normalizePath removes the Windows device namespace prefixPossibly taken A pull request linked to this issue is open or already merged. Open
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
caprover/caprover-frontend#273 ·
Maintainers usually reply within 1 day