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

[iOS] Sticky header panel covers content in a scrollview when using ReturnType="Next" on Entry fields #19956

Closed
BurkusCat opened this issue Jan 17, 2024 · 4 comments · Fixed by #20562
Assignees
Labels
area-controls-entry Entry fixed-in-8.0.10 fixed-in-9.0.0-preview.2.10293 platform/iOS 🍎 s/needs-attention Issue has more information and needs another look s/verified Verified / Reproducible Issue ready for Engineering Triage t/bug Something isn't working
Milestone

Comments

@BurkusCat
Copy link
Contributor

Description

When you have some content at the top of the page that is "sticky" and a ScrollView below. If you have Entry fields in the scroll view with the ReturnType set to "Next", when you tab through the fields the scrolling works normally. However, when you reach the final entry in the ScrollView and cycle around to the start, the "sticky" content will cover the first part of content in the ScrollView even though it is in a separate control.

Untitled.mp4

Steps to Reproduce

  1. File > New MAUI app
  2. Add the following code to your MainPage.xaml:
XAML code ``` xml ```
3. Launch the app on iOS 4. Click into the first text field 5. Tap the "next" or "enter" button until you cycle round to the first entry field

Observe issue where content in the ScrollView is covered by the sticky header despite the sticky header being an entirely separate control.

Link to public reproduction project repository

https://github.com/BurkusCat/ScrollViewKeyboardIssueIos

Version with bug

8.0.6

Is this a regression from previous behavior?

Not sure, did not test other versions

Last version that worked well

Unknown/Other

Affected platforms

iOS

Affected platform versions

iOS 15 - 17

Did you find any workaround?

No

Relevant log output

No response

@BurkusCat BurkusCat added the t/bug Something isn't working label Jan 17, 2024
@PureWeen
Copy link
Member

Can you test with the latest nightly build?
https://github.com/dotnet/maui/wiki/Nightly-Builds

@PureWeen PureWeen added the s/needs-info Issue needs more info from the author label Jan 18, 2024
@ghost
Copy link

ghost commented Jan 18, 2024

Hi @BurkusCat. We have added the "s/needs-info" label to this issue, which indicates that we have an open question for you before we can take further action. This issue will be closed automatically in 7 days if we do not hear back from you by then - please feel free to re-open it if you come back to this issue after that time.

@ghost ghost added the legacy-area-controls Label, Button, CheckBox, Slider, Stepper, Switch, Picker, Entry, Editor label Jan 18, 2024
@BurkusCat
Copy link
Contributor Author

Can you test with the latest nightly build? https://github.com/dotnet/maui/wiki/Nightly-Builds

I tried 8.0.6-nightly.9880 on the reproduction project and my actual project, both still had the same issue. I checked the .dlls to ensure the nightly was being used on the build and it was (I'm not totally familiar with VS code on Mac yet so I wanted to be sure).

@ghost ghost added s/needs-attention Issue has more information and needs another look and removed s/needs-info Issue needs more info from the author labels Jan 18, 2024
@tj-devel709
Copy link
Member

Hi @BurkusCat, I confirmed that I am able to reproduce this issue, thank you for submitting!

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
area-controls-entry Entry fixed-in-8.0.10 fixed-in-9.0.0-preview.2.10293 platform/iOS 🍎 s/needs-attention Issue has more information and needs another look s/verified Verified / Reproducible Issue ready for Engineering Triage t/bug Something isn't working
Projects
Status: Done
Development

Successfully merging a pull request may close this issue.

5 participants