[Remove Vuetify from Studio] View/Exit fullscreen buttons/links in file preview #5442

🙂 Looking for an issue? Welcome! This issue is open for contribution. If this is the first time you’re requesting an issue, please:

• Read Contributing guidelines carefully. Pay extra attention to Using generative AI. Pull requests and comments that don’t follow the guidelines won’t be answered.
• Confirm that you’ve read the guidelines in your comment.

Sub-issue of #5060.

Complexity: Low

Summary

Migrate the following file preview View/Exit fullscreen buttons/links from Vuetify to Kolibri Design System.

VBtn and shared/views/ActionLink that is built with Vuetify components are currently used to show them. To remove these Vuetify dependencies , replace the usage of VBtn and ActionLink in this specific location with the most suitable KDS button or link components. Do not modify ActionLink. Ensure that all buttons / links work exactly as before.

How to get there

• Login as a@a.com with password a
• Go to Channels > Published Channel
• Click Sample video
• In the side panel, click View fullscreen
• Close fullscreen
• Click Edit
• In the Details tab, click View fullscreen

Guidance

• Find detailed guidance with many code examples in KDS documentation
• Read the project for more useful references

Out of Scope

• Do not refactor any other areas of the codebase
• Do not modify ActionLink

Expected UI/UX changes

• Minor visual differences naturally stemming from the use of KDS

Acceptance criteria

General

• The specification above is followed.
• Except for "Expected UI/UX changes," there are no functional or visual differences in user experience.
• There are no ::v-deep or /deep/ selectors.
• All user interactions are manually tested with no regressions.
• Pull request includes screenshots.

a11y and i18n

See the project's "Guidance" for useful references.

• Implementation meets a11y standards
• All components are LTR and RTL compliant (preview with pnpm run devserver since :hot doesn't render RTL properly)
• All user-facing strings are translated properly
• The notranslate class been added to elements that shouldn't be translated by Google Chrome's automatic translation feature (e.g. user-generated text)
• Mobile experience is reasonable

Unit tests

• If there is a unit test suite already, it is meaningfully updated (even if tests don't fail)
• If there is no unit test suite, a new one is created. Do not use obsolete @vue/test-utils approach. Instead, use @testing-library/vue (Vue Testing Library).