nextcloud/server

Settings navigation: selected category out of viewable range after select

Open

#13,087 opened on Dec 15, 2018

View on GitHub
 (11 comments) (0 reactions) (0 assignees)PHP (4,865 forks)batch import
1. to developdesignenhancementfeature: settingsgood first issue

Repository metrics

Stars
 (34,953 stars)
PR merge metrics
 (Avg merge 20d) (627 merged PRs in 30d)

Description

Expected behavior

If you navigate through the settings menu categories, the last selected category should always be shown on the screen.

Current behavior

If you open the setting menu the available Personal and Administration categories are shown on the left part of the screen. If you now scroll down and select e.g. the category Administration - Logging the relevant content is correctly show on the right part of the screen but the menu itself is refreshed so that the previously selected category cannot be seen anymore.

Steps to reproduce

  1. Open the settings menu.
  2. Scroll down the menu and select the category Administration - Logging.
  3. The relevant content is correctly shown but the selected category itself is not viewable anymore because the menu is refreshed.

Environment

Server Configuration

OS: Linux 3.16.60 Web server: Apache2 2.4.37 Database: MariaDB 10.2.18 PHP version: 7.2.13 Nextcloud version: 15.0.0

Client Configuration

Browser: Mozilla Firefox 64.0 Operating system: Windows 10

Contributor guide

Research direction
Inspect the settings navigation component (likely in server/core/js or vue files) to identify where the selected category scrolls out of view after selection. Add logic to scroll the selected item into the visible area.
Tech stack
phpjavascript
Domain
backendfrontend
Issue type
Bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
GitPHPJavaScript
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
70