Skip to content

fix(files): proper accessible row name and title for overflow#61658

Merged
susnux merged 2 commits into
masterfrom
fix/files-node-name
Jul 8, 2026
Merged

fix(files): proper accessible row name and title for overflow#61658
susnux merged 2 commits into
masterfrom
fix/files-node-name

Conversation

@susnux

@susnux susnux commented Jun 29, 2026

Copy link
Copy Markdown
Contributor

Summary

In the files list before this the accessible name of the button (default action) was overridden to the default action display name. But this causes problem for screen readers because then the whole table row is just called "view" or "download" instead of using the inner text (e.g. "filename.txt").

This fixes it to rename it ACTION: FILENAME instead.

Also when long names were truncated there were no useful title (tooltip) for it, so it was not possible to get the real name. This is fixed by always provide a proper tooltip including the full name.

before after
Bildschirmfoto_20260629_163304 Bildschirmfoto_20260629_163333

Checklist

AI (if applicable)

  • The content of this PR was partly or fully generated using AI

@susnux susnux added this to the Nextcloud 35 milestone Jun 29, 2026
@susnux susnux requested review from a team and skjnldsv as code owners June 29, 2026 14:42
@susnux susnux added bug 3. to review Waiting for reviews labels Jun 29, 2026
@susnux susnux requested review from nfebe and removed request for a team June 29, 2026 14:43
@susnux susnux requested a review from sorbaugh June 29, 2026 14:43
@susnux susnux added accessibility team: Files Code maintained by 📁 Files team labels Jun 29, 2026
Comment thread apps/files/src/components/FileEntry/FileEntryName.vue Outdated
@susnux susnux force-pushed the fix/files-node-name branch from d7a3717 to 2bd8ec1 Compare June 29, 2026 15:06
Comment thread apps/files/src/components/FileEntry/FileEntryName.vue
@susnux susnux requested review from CarlSchwan and skjnldsv June 30, 2026 15:24
skjnldsv
skjnldsv previously approved these changes Jul 8, 2026
@skjnldsv skjnldsv dismissed their stale review July 8, 2026 07:08

Not fixed

@susnux

susnux commented Jul 8, 2026

Copy link
Copy Markdown
Contributor Author

Not fixed

What is not fixed?

@susnux susnux force-pushed the fix/files-node-name branch from 19b3ba7 to 957b8b7 Compare July 8, 2026 17:31
susnux added 2 commits July 8, 2026 21:33
- resolves #59203
- resolves #56611

In the files list before this the accessible name of the button (default
action) was overridden to the default action display name.
But this causes problem for screen readers because then the whole table
row is just called "view" or "download" instead of using the inner text
(e.g. "filename.txt").

This fixes it to rename it `ACTION: FILENAME` instead.

Also when long names were truncated there were no useful title (tooltip)
for it, so it was not possible to get the real name.
This is fixed by always provide a proper tooltip including the full
name.

Signed-off-by: Ferdinand Thiessen <opensource@fthiessen.de>
Signed-off-by: Ferdinand Thiessen <opensource@fthiessen.de>
@susnux susnux force-pushed the fix/files-node-name branch from 957b8b7 to e0bc30e Compare July 8, 2026 19:33
@susnux susnux merged commit 08b04d9 into master Jul 8, 2026
220 of 229 checks passed
@susnux susnux deleted the fix/files-node-name branch July 8, 2026 23:51
@susnux

susnux commented Jul 9, 2026

Copy link
Copy Markdown
Contributor Author

/backport to stable34

@susnux

susnux commented Jul 9, 2026

Copy link
Copy Markdown
Contributor Author

/backport to stable33

@backportbot

backportbot Bot commented Jul 9, 2026

Copy link
Copy Markdown

The backport to stable34 failed. Please do this backport manually.

# Switch to the target branch and update it
git checkout stable34
git pull origin stable34

# Create the new backport branch
git checkout -b backport/61658/stable34

# Cherry pick the change from the commit sha1 of the change against the default branch
# This might cause conflicts, resolve them
git cherry-pick bca2c7f2 e0bc30e6

# Push the cherry pick commit to the remote repository and open a pull request
git push origin backport/61658/stable34

Error: Failed to check for changes with origin/stable34: No changes found in backport branch


Learn more about backports at https://docs.nextcloud.com/server/stable/go.php?to=developer-backports.

@backportbot

backportbot Bot commented Jul 9, 2026

Copy link
Copy Markdown

The backport to stable33 failed. Please do this backport manually.

# Switch to the target branch and update it
git checkout stable33
git pull origin stable33

# Create the new backport branch
git checkout -b backport/61658/stable33

# Cherry pick the change from the commit sha1 of the change against the default branch
# This might cause conflicts, resolve them
git cherry-pick bca2c7f2 e0bc30e6

# Push the cherry pick commit to the remote repository and open a pull request
git push origin backport/61658/stable33

Error: Failed to check for changes with origin/stable33: No changes found in backport branch


Learn more about backports at https://docs.nextcloud.com/server/stable/go.php?to=developer-backports.

@susnux

susnux commented Jul 9, 2026

Copy link
Copy Markdown
Contributor Author

/backport bca2c7f to stable34

@backportbot

backportbot Bot commented Jul 9, 2026

Copy link
Copy Markdown

The backport to stable34 failed. Please do this backport manually.

# Switch to the target branch and update it
git checkout stable34
git pull origin stable34

# Create the new backport branch
git checkout -b backport/61658/stable34

# Cherry pick the change from the commit sha1 of the change against the default branch
# This might cause conflicts, resolve them
git cherry-pick bca2c7f2

# Push the cherry pick commit to the remote repository and open a pull request
git push origin backport/61658/stable34

Error: Failed to check for changes with origin/stable34: No changes found in backport branch


Learn more about backports at https://docs.nextcloud.com/server/stable/go.php?to=developer-backports.

@susnux

susnux commented Jul 9, 2026

Copy link
Copy Markdown
Contributor Author

/backport to stable34

@backportbot

backportbot Bot commented Jul 9, 2026

Copy link
Copy Markdown

The backport to stable34 failed. Please do this backport manually.

# Switch to the target branch and update it
git checkout stable34
git pull origin stable34

# Create the new backport branch
git checkout -b backport/61658/stable34

# Cherry pick the change from the commit sha1 of the change against the default branch
# This might cause conflicts, resolve them
git cherry-pick bca2c7f2 e0bc30e6

# Push the cherry pick commit to the remote repository and open a pull request
git push origin backport/61658/stable34

Error: Failed to check for changes with origin/stable34: No changes found in backport branch


Learn more about backports at https://docs.nextcloud.com/server/stable/go.php?to=developer-backports.

@susnux

susnux commented Jul 9, 2026

Copy link
Copy Markdown
Contributor Author

Damn the rebase broke the changes in 19b3ba7 - readd them...

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

4 participants