Swiping on smartphones and tablets
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 25/100
- Issue type
- Feature
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- javascript
- Domain
- frontend, mobile-dev
Research direction
Start with the How to Wiki pages and the current navigation behavior behind the arrow-key scrolling tip. The issue does not identify implementation files, tests, or a specific touch interaction; done would require agreeing on the mobile navigation design, implementing it, and verifying it on smartphone and tablet browsers.
Written by the indexing model from the issue text.
Description
Given that at Nov. 1, 2016, StatCounter announced ...
Internet usage by mobile and tablet devices exceeded desktop worldwide for the first time in October according to independent web analytics company
... should we consciously be giving smartphone and tablet users more love, on federated wiki?
The "How to Wiki" pages says ...
Tip: Use arrow keys to scroll left and right.
... which isn't an affordance available on my Android smartphone or tablet. The only control on a touch screen browser is the back button.
- Dominant language
- JavaScript
- Stars
- 370
- Forks
- 77
- PR merge metrics
- No merged PRs in 30d
Getting set up
- No Dockerfile or Docker Compose file
- No pull request template
- Read the contributing 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.
More from fedwiki/wiki
-
Difficulty 5/5 Over a week Newbie friendliness 35/100
-
Difficulty 5/5 Over a week Newbie friendliness 20/100
Similar issues
-
documentation good first issue theming
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
-
feature
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
drevendev/PatchPitch#2 ·
-
Difficulty 1/5 Under an hour Newbie friendliness 65/100
521xueweihan/HelloGitHub#4025 ·