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

Fix scroll buttons disabled/enabled states in the Kiosk mode #386

Merged
merged 20 commits into from
Sep 3, 2024

Conversation

matbmapspeople
Copy link
Contributor

  • I updated updateScrollButtonsState() function so it gets a proper disabled state when locations' length is lower than 8. Number 8 indicates maximum number of locations that are visible in the element without scroll.

  • Inside Search.jsx, I called newly created function newCategorySelected(). When new category is selected, and all locations to that category are rendered, we need to update disabled/enabled state of scroll buttons.

  • I performed a lot of scouting.

@ammapspeople
Copy link
Contributor

There's still some naming referring to locations and categories in the scroll buttons web component.

@matbmapspeople
Copy link
Contributor Author

There's still some naming referring to locations and categories in the scroll buttons web component.

How about now @ammapspeople

@matbmapspeople
Copy link
Contributor Author

New changes pushed @ammapspeople

@matbmapspeople
Copy link
Contributor Author

I cleaned up a little bit now and we do not use additional property. We also do not check for length. @ammapspeople

@matbmapspeople
Copy link
Contributor Author

What do you think about it now @ammapspeople ☝️

@ammapspeople
Copy link
Contributor

What do you think about it now @ammapspeople ☝️

Much better 👏

@matbmapspeople matbmapspeople merged commit f2c4d21 into main Sep 3, 2024
@matbmapspeople matbmapspeople deleted the bugfix/fix_scroll_button_in_kiosk_mode branch September 3, 2024 09:21
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants