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

Datepicker: size Input Has No Effect #17211

Closed
1 of 4 tasks
itismohammadreza opened this issue Dec 25, 2024 · 2 comments
Closed
1 of 4 tasks

Datepicker: size Input Has No Effect #17211

itismohammadreza opened this issue Dec 25, 2024 · 2 comments
Labels
Resolution: Duplicate Issue has already been reported or a pull request related to same issue has already been submitted

Comments

@itismohammadreza
Copy link
Contributor

Describe the bug

The Datepicker component includes a size input, which is expected to adjust the size of the component. However, this input appears to have no effect, as all Datepicker instances render with the same size regardless of the value provided.

image

Pull Request Link

No response

Reason for not contributing a PR

  • Lack of time
  • Unsure how to implement the fix/feature
  • Difficulty understanding the codebase
  • Other

Other Reason

No response

Reproducer

https://stackblitz.com/edit/inymwbgs

Environment

windows

Angular version

19.0.0

PrimeNG version

v19

Node version

No response

Browser(s)

No response

Steps to reproduce the behavior

  1. Bind the size input to the component with different values
  2. Observe the rendered Datepicker components in the browser.

Expected behavior

The size input for the Datepicker component should function correctly.
@itismohammadreza itismohammadreza added the Status: Needs Triage Issue will be reviewed by Core Team and a relevant label will be added as soon as possible label Dec 25, 2024
@imaksp
Copy link
Contributor

imaksp commented Dec 25, 2024

duplicate of #17199

@mertsincan mertsincan added Resolution: Duplicate Issue has already been reported or a pull request related to same issue has already been submitted and removed Status: Needs Triage Issue will be reviewed by Core Team and a relevant label will be added as soon as possible labels Dec 25, 2024
@github-actions GitHub Actions
Copy link

This issue has been marked as a duplicate and has been closed. Please refer to the original issue for updates. Thank you!

@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Dec 25, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
Resolution: Duplicate Issue has already been reported or a pull request related to same issue has already been submitted
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@imaksp @mertsincan @itismohammadreza