Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Bug]: NC 28.0.2 Context menu in "files" app does not work if scroll position is not 0 #43300

Closed
4 of 8 tasks
arnowelzel opened this issue Feb 2, 2024 · 13 comments · Fixed by #44139
Closed
4 of 8 tasks
Assignees
Labels
0. Needs triage Pending check for reproducibility or if it fits our roadmap 28-feedback bug feature: files

Comments

@arnowelzel
Copy link
Contributor

arnowelzel commented Feb 2, 2024

⚠️ This issue respects the following points: ⚠️

Bug description

If the list of files in the files app is scrolled down a bit and you try to open the context menu with the right mouse button it opens and then closes immediately again, so you can not use it.

Steps to reproduce

  1. Open a the "files" app
  2. scroll down a bit
  3. Click a file entry with the right mouse button
  4. See that the context menu opens and closes again

Expected behavior

The context menu works as expected (as in NC 28.0.1).

Installation method

Community Manual installation with Archive

Nextcloud Server version

28

Operating system

Debian/Ubuntu

PHP engine version

PHP 8.3

Web server

Apache (supported)

Database engine version

MariaDB

Is this bug present after an update or on a fresh install?

Updated from a MINOR version (ex. 22.1 to 22.2)

Are you using the Nextcloud Server Encryption module?

None

What user-backends are you using?

  • Default user-backend (database)
  • LDAP/ Active Directory
  • SSO - SAML
  • Other

Configuration report

No response

List of activated Apps

No response

Nextcloud Signing status

No response

Nextcloud Logs

No response

Additional info

No response

@arnowelzel arnowelzel added 0. Needs triage Pending check for reproducibility or if it fits our roadmap bug labels Feb 2, 2024
@arnowelzel arnowelzel changed the title [Bug]: NC 28.0.2 Context menu in "files" app does not work at all [Bug]: NC 28.0.2 Context menu in "files" app does not work if scroll position is not 0 Feb 2, 2024
@mehlkopf
Copy link

mehlkopf commented Feb 2, 2024

Having the exact same problem, independent of browser (e.g. Safari or Brave), on a Mac. This 28 version cycle is frustrating …………

@claushviid
Copy link

Having the exact same problem too.

@poiNt3D
Copy link

poiNt3D commented Feb 7, 2024

I confirm this.
It basically makes right-click menu useless.

@r4lix
Copy link

r4lix commented Feb 12, 2024

Same here, I upgraded from 26 to 28, I should have stayed with 26.

@nodiscc
Copy link

nodiscc commented Feb 18, 2024

Confirming this bug on 28.0.2.

Right-click menu is unusable after scrolling down the file list.

Steps to reproduce:

  • upload a few dozen files in a directory
  • scroll down the file list
  • right-click a file

Expected:

  • the menu stays open and allows me to select an action such as Rename, Download, etc.

What happens instead:

  • the menu closes immediately and the view scrolls back all the way up the file list

Workaround:

  • this only happens in the default list view, switching to grid/thumbnails view allows working around the problem (but is not practical as file names are truncated, I cannot see details such as file size/modification time, etc)

@MrRinkana
Copy link

MrRinkana commented Feb 19, 2024

For me the right click menu stays, but the page is instantly scrolled up.

I'm not sure how the right click menu is supposed be placed, but that looks a bit off aswell (quite far from both mouse and directory, independent of whether the scroll jumped or not).

I have not tested behaviour of scroll-jump in grid-view, but in that view the menu opens at the same location independent of which folder was rightclicked.

I'm on 28.0.2

Similar jump in scroll position at nextcloud/notes#1227

@MrRinkana
Copy link

MrRinkana commented Feb 22, 2024

Some additional findings:

The scroll jump only occurs when right-clicking the top most visible folder/file or the lowest one while in listview. The lowest one always scrolls (if you can scroll) but sometimes the lowest visible also can trigger the jump, seems to mostly trigger on the bottomost few.

In gridview it seems less predictable, sometimes right-clicking the topmost visible makes it jump down for example. Clicking the bottommost can trigger the jump, but only if it is alone on the last row (?).

I mentioned that the rightclick menu opens in only one location but that is not completely true, as clicking the topmost row produces one location, the rest another (to two locations in total). Sometimes reloading the page fixes the weird location problem, albeit now the options are highlighted as if some accessibility option got turned on.

In essence; things are weird 😅

EDIT: Tested with Edge aswell (Firefox before), and behaviour is still there, with some slight changes in how the right-click menu appears, and which folders trigger the jump in gridview.

@wargreen
Copy link

Similar jump in scroll position at nextcloud/notes#1227

Same thing happen with the pdf viewer.

@theosche
Copy link

theosche commented Mar 1, 2024

Having the exact same problem, independent of browser (e.g. Safari or Brave), on a Mac. This 28 version cycle is frustrating …………

I also have this problem with 28.0.3 using Firefox (123.0) and Safari (16.5.1), but the menu works on Chrome (122.0.6261.94).

@refda
Copy link

refda commented Mar 1, 2024

I was testing the right click menu again with 28.0.3 in Firefox and Chrome: Both are not working when it comes to the position, please see #43842

@MrRinkana
Copy link

Maybe nextcloud/notes#1227 should be closed aswell, since it seems fixed and i suspect it was fixed by the same changes

@Pytal
Copy link
Member

Pytal commented Apr 2, 2024

The fix seems unrelated as #44139 only touches files code which does not interfere with notes code

If the issue cannot be reproduced anymore though, feel free to close it @MrRinkana

@MrRinkana
Copy link

You're right, it was fixed by nextcloud/text#5281

I cannot close the issue, but I made a comment asking op to close if it no longer reproduces

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
0. Needs triage Pending check for reproducibility or if it fits our roadmap 28-feedback bug feature: files
Projects
None yet
Development

Successfully merging a pull request may close this issue.