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.

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

InputMask: Not filling up to 100% in combination with InputGroup and w-full PrimeFlex class #14478

Closed
msg-ptavoul opened this issue Jan 4, 2024 · 2 comments
Labels
Resolution: Stale Issue or pull request is inactivity and unfortunately it will be *closed* if there is no response Type: Bug Issue contains a bug related to a specific component. Something about the component is not working

Comments

@msg-ptavoul
Copy link

Describe the bug

If we put an InputMask inside an InputGroup the InputMask width is very small.
So the InputMask is not filling up to 100% (it's more like 1%).

We tried to use the PrimeFlex class "w-full" to set the width up to 100%.
But that is not working...

Old PrimeNg Issue:
#14404

After the release the problem was not fixed...

Environment

Windows 11

Reproducer

https://stackblitz.com/edit/stackblitz-starters-1l7ghs

Angular version

17.0.8

PrimeNG version

17.3.0

Build / Runtime

Angular CLI App

Language

TypeScript

Node version (for AoT issues node --version)

20.9.0

Browser(s)

119.0.6045.200

Steps to reproduce the behavior

  1. Write an InputGroup Wrapper
  2. Put an InputMask inside the wrapper
  3. Run the Project and check the view
  4. Put the PrimeFlex class "w-full" into the InputMask and check again the view - nothing happened

Expected behavior

No response

@msg-ptavoul msg-ptavoul added the Status: Needs Triage Issue will be reviewed by Core Team and a relevant label will be added as soon as possible label Jan 4, 2024
@mehmetcetin01140 mehmetcetin01140 added Type: Bug Issue contains a bug related to a specific component. Something about the component is not working and removed Status: Needs Triage Issue will be reviewed by Core Team and a relevant label will be added as soon as possible labels Jan 5, 2024
Copy link

github-actions bot commented May 5, 2024

This issue has been automatically marked as stale. If this issue is still affecting you with the latest version, please leave any comment, and we will keep it open. We are sorry that we have not been able to prioritize it yet. If you have any new additional information, please include it with your comment!

@github-actions github-actions bot added the Resolution: Stale Issue or pull request is inactivity and unfortunately it will be *closed* if there is no response label May 5, 2024
Copy link

Closing this issue after a prolonged period of inactivity. If this issue is still present in the latest release, please create a new issue with up-to-date information. Thank you for your understanding!

@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale May 12, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Resolution: Stale Issue or pull request is inactivity and unfortunately it will be *closed* if there is no response Type: Bug Issue contains a bug related to a specific component. Something about the component is not working
Projects
None yet
Development

No branches or pull requests

2 participants