Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

<b-form-datepicker> cannot use <b-calendar> dateInfoFn #4826

Closed
juliusvdijk opened this issue Feb 25, 2020 · 1 comment · Fixed by #5150 · May be fixed by leonyork/cognito-oauth2-demo#1
Closed

<b-form-datepicker> cannot use <b-calendar> dateInfoFn #4826

juliusvdijk opened this issue Feb 25, 2020 · 1 comment · Fixed by #5150 · May be fixed by leonyork/cognito-oauth2-demo#1
Labels
Priority: Low Status: Fixed / Implemented Issue fixed by a new release Type: Feature request

Comments

@juliusvdijk
Copy link

Is your feature request related to a problem? Please describe...

I expect the dateInfoFn prop, which is present in , to also be available in

Describe the solution you'd like

Add dateInfoFn to the props of and pass it through to

Describe alternatives you've considered

None.

Additional context
@tmorehouse
Copy link
Member

Currently, we do not have a means of providing feedback to users of screen readers to signify meaning to the class being applied by dateInfoFn to specific dates, which is why dateInfoFn was specifically left out of the datepicker component (for now)

tmorehouse added a commit that referenced this issue Apr 15, 2020
@tmorehouse
feat(b-form-datepicker): add pass through prop date-info-fn (closes #…
7357f44 
…4826)
This was referenced Apr 15, 2020
Merged
Merged
tmorehouse added a commit that referenced this issue Apr 15, 2020
@tmorehouse
feat(b-form-datepicker): add pass through prop date-info-fn (closes #…
bf35f80 
…4826) (#5150)
@snyk-bot snyk-bot mentioned this issue Apr 30, 2020
Open
@tmorehouse tmorehouse added the Status: Fixed / Implemented Issue fixed by a new release label May 10, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
Priority: Low Status: Fixed / Implemented Issue fixed by a new release Type: Feature request
Projects
None yet
Milestone
No milestone
2 participants
@juliusvdijk @tmorehouse