nextcloud / nextcloud/logreader
Expanded entry shifts in live view
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 69
- Forks
- 30
- Avg merge
- 10h 28m
- Merged PRs (30d)
- 57
Description
Steps to reproduce
- Open the log reader
- Expand an entry of interest
- A new log appears
Expected behaviour
The expanded entry stays expanded
Actual behaviour
As the list moves, the expanded entry shifts by the number of new log entries pulled.
From a technical POV it looks like expanded/collapsed is tracked by index, not an ID of the entries.
Server configuration
Operating system:
Web server:
Database:
PHP version:
Nextcloud version: 30
Where did you install Nextcloud from:
List of activated apps:
If you have access to your command line run e.g.:
sudo -u www-data php occ app:list
from within your Nextcloud installation folder
Nextcloud configuration:
If you have access to your command line run e.g.:
sudo -u www-data php occ config:list system
from within your Nextcloud installation folder
or
Insert your config.php content here
Make sure to remove all sensitive content such as passwords. (e.g. database password, passwordsalt, secret, smtp password, …)
Client configuration
Browser:
Operating system:
Logs
Nextcloud log (data/owncloud.log)
Insert your Nextcloud log here
Browser log
Insert your browser log here, this could for example include:
a) The javascript console log
b) The network log
c) ...
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 issue in the log reader: expand an entry, then allow a new log entry to appear. Trace how expanded and collapsed state is associated with entries, and consider the work done when the same entry remains expanded as new logs are pulled.
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
- 42/100