[Bug]: RTL/Farsi popover positioning bug in Files app on Nextcloud 34.0.1
Nobody has claimed this yet.
- Dominant language
- PHP
- Stars
- 36.9k
- Forks
- 5.2k
- Avg merge
- 2d 3h
- Merged PRs (30d)
- 713
Description
⚠️ This issue respects the following points: ⚠️
- This is a bug, not a question or a configuration/webserver/proxy issue.
- This issue is not already reported on Github OR Nextcloud Community Forum (I've searched it).
- Nextcloud Server is up to date. See Maintenance and Release Schedule for supported versions.
- I agree to follow Nextcloud's Code of Conduct.
Bug description
In Nextcloud 34.0.1, the Files app popover/dropdown is positioned incorrectly when the UI language is set to Persian (RTL). The same action works correctly in English (LTR), so this appears to be an RTL-specific frontend positioning bug.
Actual result:
The popover is rendered in the upper-right area and overlaps the right navigation sidebar / wrong boundary area.
Environment:
- Nextcloud: 34.0.1
- UI language: Persian (RTL)
- In English (LTR): works correctly
- Affects Files app / share popover / dropdown positioning
Steps to reproduce
1.1. Set Nextcloud UI language to Persian.
2. Open Files.
3. Open a file details/share popover or dropdown.
4. Observe that the menu opens in the wrong position, overlapping the right sidebar instead of appearing next to the clicked control.
2.
3.
Expected behavior
The popover should open aligned with its trigger and remain inside the viewport, respecting RTL layout.
Nextcloud Server version
34
Operating system
Debian/Ubuntu
PHP engine version
PHP 8.4
Web server
Nginx
Database engine version
PostgreSQL
Is this bug present after an update or on a fresh install?
Fresh Nextcloud Server install
Are you using the Nextcloud Server Encryption module?
Encryption is Disabled
What user-backends are you using?
- Default user-backend (database)
- LDAP/ Active Directory
- SSO - SAML
- Other
Configuration report
List of activated Apps
Nextcloud Signing status
Nextcloud Logs
Additional info
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 Files app with the UI language set to Persian, then inspect the share popover or dropdown positioning relative to its trigger and the right sidebar. Done means the popover stays aligned with its trigger and inside the viewport in RTL while preserving the existing English behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- frontend, internationalization
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100