Skip to content

Conversation

sebmue-dataport
Copy link
Contributor

@sebmue-dataport sebmue-dataport commented Aug 25, 2025

Short Description

  • Fix: Pressing escape instead of clicking the cancel button in the Room Copy Info Dialog caused the dialog to close but kept it from ever being opened again in the same session. Fixed by using after-leave on VDialog
  • Refactor: Several legacy uses of $t for using i18n replaced with t
  • Refactor: Simplify the Share Dialog and remove dependency towards Custom Dialog using VDialog instead

Links to Ticket and related Pull-Requests

https://ticketsystem.dbildungscloud.de/browse/BC-10453

Checklist before merging

  • QA: In addition to review, the code has been manually tested (if manual testing is possible)
  • PO: Any deviation from requirements was agreed with Product-Owner / ticket author / support-team
  • DEV: Every new component is implemented having accessibility in mind (e.g. aria-label, role property)
  • Cypress: Every new feature has suitable Cypress tests implemented

@sebmue-dataport sebmue-dataport changed the title Bc 10453 a11y fixes WIP: BC-10453 a11y fixes Aug 25, 2025
@sebmue-dataport sebmue-dataport changed the title WIP: BC-10453 a11y fixes WIP: BC-10453 Minor a11y fixes Aug 25, 2025
<script setup lang="ts">
import { ModelRef, PropType } from "vue";
export type VCustomDialogButton =
Copy link
Contributor

Choose a reason for hiding this comment

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

Please check if other usages of VCustomDialog need to be refactored to this type, too.

`[data-testid="share-modal-external-tools-info"]`
);

expect(infotext.isVisible()).toBe(true);
Copy link
Contributor

Choose a reason for hiding this comment

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

Was this invisible-check removed intentionaly?

@next="onNext()"
<v-dialog
v-model="isOpen"
data-testid="sharedialog"
Copy link
Contributor

Choose a reason for hiding this comment

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

Ensure that changing the data-testid does not have impact on e2e-tests for example... or just keep it as it was.

v-model="isOpen"
data-testid="sharedialog"
max-width="480"
@after-leave="onCleanUp"
Copy link
Contributor

Choose a reason for hiding this comment

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

I would keep the naming

Suggested change
@after-leave="onCleanUp"
@after-leave="onCloseDialog"

as the name should describe the event not the actions that are taken in the case of the event.

{{
t("components.molecules.share.options.tableHeader.InfoText")
}}
<ul class="ml-6">
Copy link
Contributor

Choose a reason for hiding this comment

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

Are the combinations tested - to ensure that the right list items are shown for each setting being true - and "no setting true"?

<share-modal-result
:share-url="shareUrl"
:type="type"
@done="onCloseDialogOrDone"
Copy link
Contributor

Choose a reason for hiding this comment

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

Same as above eventName.

};
const onNext = () => {
// shareModule.createShareUrl({ isSchoolInternal: false, hasExpiryDate: false });
Copy link
Contributor

Choose a reason for hiding this comment

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

Remove comments

const showRoomInfo = computed(() => {
return props.type === "room";
const listItems = computed(() => {
Copy link
Contributor

Choose a reason for hiding this comment

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

The readabilty in the template code was increased... but this config-part is not (very much) more readable and reduces extendability...

<v-card data-testid="copy-info-dialog">
<UseFocusTrap>
<v-card-title>
<h2 class="mt-2 text-break">
Copy link
Contributor

@NFriedo NFriedo Oct 17, 2025

Choose a reason for hiding this comment

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

While merging main into this branch, the title was changed to h2.

We should check if we need px-6 pt-4

@sonarqubecloud
Copy link

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

Labels

None yet

Development

Successfully merging this pull request may close these issues.

3 participants