Skip to content

fix: introduce UI toggle to allow/disallow updating#18497

Merged
Antreesy merged 1 commit into
mainfrom
fix/18485/share-with-update-frontend
Jul 4, 2026
Merged

fix: introduce UI toggle to allow/disallow updating#18497
Antreesy merged 1 commit into
mainfrom
fix/18485/share-with-update-frontend

Conversation

@Antreesy

@Antreesy Antreesy commented Jun 30, 2026

Copy link
Copy Markdown
Contributor

☑️ Resolves

AI (if applicable)

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

🖌️ UI Checklist

🖼️ Screenshots / Screencasts

🏚️ Before 🏡 After
Screenshot before 2026-07-03_16h39_07

🚧 Tasks

  • Default is 'off'?

🏁 Checklist

  • 🌏 Tested with different browsers / clients:
    • Chromium (Chrome / Edge / Opera / Brave)
    • Firefox
    • Safari
    • Talk Desktop
    • Integrations with Files sidebar and other apps
    • Not risky to browser differences / client
  • 🖌️ Design was reviewed, approved or inspired by the design team
  • ⛑️ Tests are included or not possible
  • 📗 User documentation in https://github.com/nextcloud/documentation/tree/master/user_manual/talk has been updated or is not required[skip ci]

Signed-off-by: Maksim Sukharev antreesy.web@gmail.com

@Antreesy Antreesy added this to the ⛅ Next Major (35) milestone Jun 30, 2026
@Antreesy Antreesy requested a review from nimishavijay June 30, 2026 08:59
@Antreesy Antreesy self-assigned this Jun 30, 2026
@Antreesy Antreesy added bug feature: frontend 🖌️ "Web UI" client feature: upload & shares & voice 📤🎙️ Sharing files into a chat and audio recordings labels Jun 30, 2026
@nickvergessen nickvergessen force-pushed the bugfix/18354/allow-sharing-with-update-permissions branch 3 times, most recently from b0670ac to 20944dd Compare July 1, 2026 05:39
@nimishavijay

nimishavijay commented Jul 1, 2026

Copy link
Copy Markdown
Member

Why are we not always allowing editing? 🤔 There is no switch to allow editing for text, so this extra switch feels a bit disruptive. We should indicate that a file has been edited always in the message, though. If we do want a switch I would suggest we keep it enabled by default and a bit more hidden, what do you think?

Base automatically changed from bugfix/18354/allow-sharing-with-update-permissions to main July 1, 2026 16:30
@nickvergessen

Copy link
Copy Markdown
Member

Why are we not always allowing editing?

We had reports before, especially when sharing screenshots and images it's totally unexpected that others can replace/edit them.
And also in no other messenger is the default "everyone in this room can modify my shared content"

We should indicate that a file has been edited always in the message, though.

Not technically possible

If we do want a switch I would suggest we keep it enabled by default and a bit more hidden, what do you think?

As per team week discussion we are most likely going to add a compression toggle anyway, so it would just be 2 for now.

@nimishavijay

Copy link
Copy Markdown
Member

We had reports before, especially when sharing screenshots and images it's totally unexpected that others can replace/edit them. And also in no other messenger is the default "everyone in this room can modify my shared content"

Is it "everyone in the room" or just moderators? What would be the use case for others being able to edit the image? If it is technically not possible then maybe we just don't allow editing for images for the sake of transparency?

Taking a quick look at Teams, Slack, Google Workspace Chat and Discord don't allow others to edit even text messages in the first place. This switch being so present is asking the user to make another decision before the simple and very commonly used action of sending an image.

@Antreesy

Antreesy commented Jul 2, 2026

Copy link
Copy Markdown
Contributor Author

Is it "everyone in the room" or just moderators?

Everyone got write permissions before, if file uploaded directly to Talk

What would be the use case for others being able to edit the image?

Organisations working with visual materials / marketing maybe?

Maybe we just don't allow editing for images for the sake of transparency?

That sounds like another way of working around current behaviour (everything is read-only, if you need editing - share from Files app). Also video/audio could fall into that category. Or the other way around, somehow receive list of office-provided filetype (+ .txt .md files), and allow edit them by default - but I agree now that is also subtle and non-obvoius behaviour

This switch being so present

We can default back to legacy switches (toggle on the left side, smaller) or checkboxes

@Antreesy Antreesy force-pushed the fix/18485/share-with-update-frontend branch from 92ff5f9 to 39240aa Compare July 2, 2026 13:40
@Antreesy Antreesy marked this pull request as ready for review July 3, 2026 13:50
@Antreesy Antreesy requested review from DorraJaouad and ShGKme July 3, 2026 17:22

@ShGKme ShGKme left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

All good code-wise

@DorraJaouad DorraJaouad left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Tested, yet I am not sure if showing this toggle for images /videos only shares is good

Signed-off-by: Maksim Sukharev <antreesy.web@gmail.com>
@Antreesy Antreesy force-pushed the fix/18485/share-with-update-frontend branch from aba58be to 6576763 Compare July 4, 2026 12:00
@Antreesy Antreesy merged commit cd1c20f into main Jul 4, 2026
54 checks passed
@Antreesy Antreesy deleted the fix/18485/share-with-update-frontend branch July 4, 2026 12:22
@Antreesy

Antreesy commented Jul 4, 2026

Copy link
Copy Markdown
Contributor Author

/backport to stable34

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

Labels

bug feature: frontend 🖌️ "Web UI" client feature: upload & shares & voice 📤🎙️ Sharing files into a chat and audio recordings

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants