Skip to content

Conversation

@odalys-dataport
Copy link
Contributor

Short Description

Links to Ticket and related Pull-Requests

Changes

Data-security

Deployment

New Repos, NPM packages or vendor scripts

Screenshots of UI changes

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

Notice: Please keep this Pull-Request as a Draft (or add WIP label), until it is ready to be reviewed

@odalys-dataport odalys-dataport self-assigned this Nov 20, 2025
export type FabAction = {
icon: string;
label: string;
ariaLabel?: string;
Copy link
Contributor

Choose a reason for hiding this comment

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

I think ive seen, that the label and the arialabel were filled with the same values.
Which either makes the arialabel obsulete as a prop or should have better values.

I generally would love to see, that aria stuff is working without special treatment.

wrapper.setProps({ icon: mdiClose });
const btn = wrapper.getComponent(VFab).getComponent(VBtn);
logger.log(btn.classes());
expect(btn.classes()).toContain("rounded-circle");
Copy link
Contributor

Choose a reason for hiding this comment

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

Hm somewhat goes into same direction as in one of the other comments -> shall we instead test against the prop, instead of the classes?

The menu should forceToCollapseOnMobileScroll, no?

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