palantir/blueprint

DatePicker disabled/readOnly state

Open

#5,008 opened on Nov 3, 2021

View on GitHub
 (1 comment) (0 reactions) (0 assignees)TypeScript (20,263 stars) (2,167 forks)batch import
P2Package: datetimeType: enhancementhelp wanted

Description

Environment

  • Package version(s): @blueprintjs/datetime 3.23.15
  • Browser and OS versions: N/A (let me know if you need this for whatever reason)

Question

Is there a way to put the DatePicker component into a disabled/readOnly state? I've found that I can put all days in a disabled state like so:

<DatePicker dayPickerProps={{disabledDays: () => true}}/>

But then the user can still interact with the month/year controls.

image

Contributor guide

Tech stack
typescriptreact
Domain
frontend
Issue type
feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-2 days
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
needs investigation
Prerequisites
React basicsBlueprint component structure
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
40
Research direction
Investigate the DatePicker component in @blueprintjs/datetime (likely src/datePicker.tsx) to understand how interaction is handled. Check if there are existing props that can be leveraged, and consider how a new disabled prop would disable both day selection and month/year controls. Review any related comments or PRs for prior discussion.