nextcloud / nextcloud/tables

First search on any of multiple views in an application filters all views

Open
#3,008 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

0. Needs triage bug
Dominant language
JavaScript
Stars
214
Forks
52
Avg merge
1d 10h
Merged PRs (30d)
82

Description

Steps to reproduce
  1. create two views of the same table
  2. create an application with both of the views
  3. use the search field atop ONE view
  4. clear that search term
  5. search for another search term
  6. add a letter into other views´ search input (being empty before)
  7. remove that letter
Expected behavior
  1. ...
  2. ...
  3. only the active view must be filtered by the search term entered into the search input above that ONE view.
  • other views keep being uninterrupted
  1. that ONE view gets un-filtered
  • other views keep being uninterrupted
  1. the input on the ONE search input DID never affect the other views
  2. other views keep being uninterrupted
  3. other views keep being uninterrupted
Actual behavior
  1. ...
  2. ...
  3. all views are filtered by the search term entered into the search input above ONE view.
  • other search input fields are empty though active
  1. that ONE view gets un-filtered
  • other views keep being filtered
  1. NOW the input on the ONE search input DOES NOT affect the other views anymore
  2. other views keep that "wrong filter"
  3. other views get unfiltered at last
Tables app version

2.3.0

Browser

Vivaldi 8.2.4133.52

Client operating system

Windows 11

Operating system

Nextcloud Hub 26 Spring (34.0.3)

Web server

No response

PHP engine version

Other

Database

MySQL

Additional info

No response

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 with two views of the same table inside one application, following the listed search and clearing steps. Trace how each view's search input and filter state are handled. Done means typing, clearing, or editing one view's search affects only that view and leaves the others unchanged.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript
Domain
frontend, web-dev
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Active
Clarity
Mostly clear
Newbie friendliness
65/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.