NUKnightLab / NUKnightLab/TimelineJS3
Configurable management of slide navigation
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 3.2k
- Forks
- 645
- PR merge metrics
- No merged PRs in 30d
Description
Per Zendesk ticket 3223, slide navigation on mobile screens can sometimes feel overly "sensitive", likely an indication that the touch area of the navigation is not optimal (although this diagnosis still needs to be fully investigated).
Some potential solutions to consider are (1) to make the touch area size of navigation elements configurable, or (2) as per the subject line of 3223, to make the touch navigation optional, (presumably relying instead on swipe navigation).
The right solution, and even the breadth of the problem will need to be understood in order to move forward on this. This issue will likely need to be investigated on a number of timelines and a number of screens/devices.
For reference, the timeline of ticket 3223 is: https://saturn.jpl.nasa.gov/the-journey/timeline/
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
No files, tests, or entry points are named. Begin by reproducing the sensitive navigation on mobile screens and devices, using Zendesk ticket 3223 and the referenced Saturn timeline as examples. Compare configurable touch areas with optional touch navigation; done requires an agreed solution and verified behavior across the affected cases.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- frontend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100