NUKnightLab / NUKnightLab/TimelineJS3
Proper support for systems which support *both* touch and mouse interface.
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 3.2k
- Forks
- 645
- PR merge metrics
- No merged PRs in 30d
Description
A Zendesk user reported problems using Chrome and Firefox on a Microsoft Surface device:
I just have one question and i'm hoping it's a problem on my side: I can only swipe on my screen to navigate, but I want to use the mouse to navigate/scroll. Is this disabled or a bug?
I’m having this issue on a Microsoft Surface 3 with Win 8.1 and Chrome version: Version 44.0.2403.107 m (64-bit)
I don't have access to a Surface or other Windows device that supports both mouse and touch, but I would not be surprised if Timeline assumes touch == !mouse
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 reproducing the reported navigation problem in Chrome or Firefox on a device that supports both mouse and touch, such as a Microsoft Surface. Inspect TimelineJS's touch and mouse input handling, especially the assumption that touch implies no mouse. Done means mouse navigation and scrolling work alongside touch interaction on the same device.
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