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

Component: p-float-label not displaying correctly in multicolumn unordered list. #15402

Closed
4gDad opened this issue Apr 29, 2024 · 1 comment
Closed
Labels
Status: Needs Triage Issue will be reviewed by Core Team and a relevant label will be added as soon as possible

Comments

@4gDad
Copy link

4gDad commented Apr 29, 2024

Describe the bug

When you have a multiple column unordered list the first float label in the second column shows at the bottom of the first column.

image

Environment

na

Reproducer

No response

Angular version

17.3.5

PrimeNG version

17.14.1

Build / Runtime

TypeScript

Language

ALL

Node version (for AoT issues node --version)

?

Browser(s)

Edge

Steps to reproduce the behavior

Create an and list with multiple items like this.





  • Access Code 1





  • Access Code 2





  • Access Code 3





  • Access Code 4





  • Access Code 5





  • Access Code 6





  • Access Code 7





  • Access Code 8





  • Access Code 9





  • Access Code 10


Make the list multipe columns like this via css

.access-code-list{
list-style-type: none;
margin-top: 20px;

 -moz-column-count: 3;
 -moz-column-gap: 20px;
 -webkit-column-count: 3;
 -webkit-column-gap: 20px;
 column-count: 3;
 column-gap: 20px;

}

Select the first item in the second column and see the floating label show up at the bottom of the first column

Expected behavior

The floating label should show on top of the first item in the second column.

@4gDad 4gDad added the Status: Needs Triage Issue will be reviewed by Core Team and a relevant label will be added as soon as possible label Apr 29, 2024
@mertsincan
Copy link
Member

Hi,

So sorry for the delayed response! Improvements have been made to many components recently, both in terms of performance and enhancement. Therefore, this improvement may have been developed in another issue ticket without realizing it. You can check this in the documentation. If there is no improvement on this, can you open a new issue so we can include it in our roadmap?

Thanks a lot for your understanding!
Best Regards,

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Status: Needs Triage Issue will be reviewed by Core Team and a relevant label will be added as soon as possible
Projects
None yet
Development

No branches or pull requests

2 participants