nextcloud / nextcloud/logreader

Mobile browser: Panning in details view switches log entry in details view

Open
#1,447 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

0. Needs triage bug
Dominant language
JavaScript
Stars
69
Forks
30
Avg merge
10h 28m
Merged PRs (30d)
57

Description

How to use GitHub
  • Please use the 👍 reaction to show that you are affected by the same issue.
  • Please don't comment if you have no relevant information to add. It's just extra noise for everyone subscribed to this issue.
  • Subscribe to receive notifications on status change and new comments.

Steps to reproduce

1.open log viewer on mobile browser
2.open details view of a log entry
3.scroll left right to read full message

Expected behaviour

When moving the content of the log entry it should scroll left/right to read the full post, longer lines for example.

Actual behaviour

Details Viewer switches next/previous ends and it is hard to read full text of one entry. There are buttons for this action, so swipe gesture is not needed.

Server configuration

Web server:
Apache
Database:
Mariadb
PHP version:
8.3
Nextcloud version: (see Nextcloud admin page)
30.0.4

List of activated apps
Not relevant
Nextcloud configuration
Not relevant
Browser

Browser name:
All mobile browsers, tested on Chrome, Firefox and DuckDuck Go

Browser version: 124/125/…

Operating system: Windows/Ubuntu/Mac/…
Android

Browser log
Not relevant

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reproducing the issue in the log viewer's details view on an Android mobile browser, swiping horizontally across a long log message. Trace the details-view touch or swipe handling and distinguish content scrolling from next/previous entry navigation. Done means horizontal panning reads the full message without switching entries, while the existing navigation buttons still work.

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
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.