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

Using TabType="Scrollable" missing scroll/focus #9

Open
renelaerke opened this issue Nov 3, 2020 · 3 comments
Open

Using TabType="Scrollable" missing scroll/focus #9

renelaerke opened this issue Nov 3, 2020 · 3 comments
Labels
enhancement New feature or request

Comments

@renelaerke
Copy link

I'm very fond of this component which i find very flexible and performant. Thank you !

However i miss the functionality to automatically (or by calling a build-in method inside OnSelectedIndexChanged) to "automatically" scroll the TabHostView to the currently selected TabItem

Whether I set the SelectedIndex via code to an index currently not visible (not scrolled into view) OR the user "taps" on a partly visible TabItem - the TabHostView is not automatically scrolling the TabItem to be fully visible.

I may very well be missing setting a Property on TabHostView to some "magic" value - but I did consult the sources on github - and i couldn't find either a method nor something that seem to ask the private _scrollView to scroll items to be visible.

What am I missing ?

Regards René

@roubachof
Copy link
Owner

you are missing nothing, it lacks the functionality :)

@roubachof roubachof added the enhancement New feature or request label Jan 18, 2021
@vhugogarcia
Copy link

Hello @renelaerke were you able to implement this functionality somehow? I'm also trying to implement it.

Thanks in advance

@renelaerke
Copy link
Author

Sorry, but no.

Instead we had to restructure our data-design.

😬 René

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants