vuetifyjs / vuetifyjs/vuetify

[Bug Report][3.8.1] V-Card missing "active" properties for being used as a link

Open
#21,235 0 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

C: VCard T: feature
Dominant language
TypeScript
Stars
41k
Forks
7.1k
Avg merge
1d 21h
Merged PRs (30d)
11

Description

Environment

Vuetify Version: 3.8.1
Vue Version: 3.5.13
Browsers: Chrome 134.0.0.0
OS: Windows 10

Steps to reproduce
  1. Create a set of clickable v-card components that link to routes in the vue-router.
  2. Click on the cards.
Expected Behavior

The cards should have some way to see which one corresponds to the active route, consistent with v-breadcrumbs, v-btn, v-chip, and v-list-item.

Actual Behavior

There is no way to see that the v-card points to the active route.

Reproduction Link

https://play.vuetifyjs.com/#...

Other comments

The documentation says:

The following components have built in support for routing:

  • v-breadcrumbs
  • v-btn
  • v-card
  • v-chip
  • v-list

These components can act like a router-link and have access to props such as to and exact

It does not say anywhere that v-card is different than the other four components.

The fact that v-card does have the exact property implies that the missing active (and active-class, etc.) is an oversight, not a conscious decision.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the v-card routing behavior shown in the reproduction link and compare it with the routing support described in the documentation link for v-btn, v-chip, and v-list-item. Confirm which active-route behavior is missing for clickable v-card components, then verify that the cards expose and apply the expected active state consistently.

Written by the indexing model from the issue text.

Assessment

Tech stack
typescript
Domain
frontend
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.