NUKnightLab / NUKnightLab/TimelineJS3
Year Cutoff on Firefox/Chrome
Open
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 3.2k
- Forks
- 645
- PR merge metrics
- No merged PRs in 30d
Description
I noticed on my timeline and on the demo one from Knightlab's site. The year at the bottom is cutoff in at least Firefox and Chrome on MacOS. However if you scroll past the timeline and then go back to it, it displays properly.
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
Reproduce the cutoff on the reported timeline and Knightlab demo in Firefox and Chrome on macOS, then trace the timeline's year rendering and layout behavior. Compare the initial display with the state after scrolling away and back. Done means the year at the bottom displays fully on the first view and remains correct after returning to the timeline.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- frontend
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100