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

Carousel: Carousel elements do not recalculate after changing screen orientation #5805

Closed
prakhar217 opened this issue Jan 19, 2024 · 1 comment
Labels
Resolution: Duplicate Issue has already been reported or a pull request related to same issue has already been submitted

Comments

@prakhar217
Copy link

Describe the bug

When changing the screen Orientation when we have different number of visible for the two orientation , the width doesnt re calculate
For eg for a landscape screen size if we have lets say 3 elements visible but for a portrait mode the count is 2 , but when we again use the landscape , the button remains active according the amount of tiimes it was needed to scroll for the portrait mode

const responsiveOptions: CarouselResponsiveOption[] = [ { breakpoint: "1366px", numVisible: 3, numScroll: 3, }, { breakpoint: "1200px", numVisible: 3, numScroll: 3, }, { breakpoint: "1180px", numVisible: 3, numScroll: 3, }, { breakpoint: "1024px", numVisible: 2, numScroll: 2, }, { breakpoint: "991px", numVisible: 2, numScroll: 2, }, { breakpoint: "767px", numVisible: 2, numScroll: 2, }, ];

Reproducer

No response

PrimeReact version

10.1.1

React version

17.x

Language

TypeScript

Build / Runtime

Create React App (CRA)

Browser(s)

No response

Steps to reproduce the behavior

No response

Expected behavior

it should change scroll according to item number displayed

@prakhar217 prakhar217 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 19, 2024
@melloware
Copy link
Member

Duplicate of: #5166

@melloware melloware closed this as not planned Won't fix, can't repro, duplicate, stale Jan 19, 2024
@melloware melloware 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 Jan 19, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Resolution: Duplicate Issue has already been reported or a pull request related to same issue has already been submitted
Projects
None yet
Development

No branches or pull requests

2 participants