Skip to content

Conversation

@J-Sek
Copy link
Contributor

@J-Sek J-Sek commented Nov 6, 2025

  • added missing adapter.date(...) around props.min and props.max
  • extracted into reusable composable
  • changed to avoid clamping multiple (non-range) - it is confusing to when input field says 2 selected, but the picker shows only one day

fixes #22291

Markup:

<template>
  <v-app theme="dark">
    <v-container>
      <v-alert>
        paste: <v-code>09/09/2025</v-code> or <v-code>01/02/2026</v-code>
      </v-alert>
      <v-date-input label="Date input" max="2025-11-11" />
    </v-container>
    <v-container>
      <v-alert>
        paste: <v-code>09/09/2025</v-code> or <v-code>11/01/2025, 11/08/2025, 11/15/2025</v-code>
      </v-alert>
      <v-date-input label="Date input" max="2025-11-11" multiple />
    </v-container>
    <v-container>
      <v-alert>
        paste: <v-code>09/09/2025</v-code> or <v-code>11/07/2025 - 11/14/2025</v-code>
      </v-alert>
      <v-date-input label="Date input" max="2025-11-11" multiple="range" />
    </v-container>
  </v-app>
</template>

@J-Sek J-Sek self-assigned this Nov 6, 2025
@J-Sek J-Sek added T: bug Functionality that does not work as intended/expected C: VDateInput labels Nov 6, 2025
@J-Sek J-Sek force-pushed the fix/vdateinput-min-max branch from 99799af to ad75fac Compare November 6, 2025 05:28
@J-Sek J-Sek merged commit e67c411 into master Nov 8, 2025
18 checks passed
@J-Sek J-Sek deleted the fix/vdateinput-min-max branch November 8, 2025 11:16
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

C: VDateInput T: bug Functionality that does not work as intended/expected

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[Bug Report] v-date-input with max attribute fails with keyboard entry

2 participants