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

UI Elements Overlap on iOS 14 and 15 #7

Open
MussaCharles opened this issue Jul 23, 2023 · 1 comment
Open

UI Elements Overlap on iOS 14 and 15 #7

MussaCharles opened this issue Jul 23, 2023 · 1 comment

Comments

@MussaCharles
Copy link

MussaCharles commented Jul 23, 2023

Hi,

Firstly, thanks for your work on this library - it's been incredibly useful.

I've noticed an issue where UI elements are overlapping when the library is used on iOS 14 and 15. The same problem doesn't appear on iOS 16. Here are some screenshots to illustrate:

See iOS version at the top of each simulator, from left to right (iOS 14.x, iOS 15.x, iOS 16.x)
Screenshot 2023-07-23 at 12 40 12 PM

                WrapLayout(horizontalSpacing: 4, verticalSpacing: 8) {
                    Text("First")
                    
                    HStack(alignment: .center, spacing: 0) {
                        Text("Top content")
                        
                        Text(",")
                    }
                    
                    HStack(alignment: .center, spacing: 0) {
                        Button {
                            
                        } label: {
                            Text("Underlined 1.")
                                .underline()
                        }
                        Text(",")
                    }
                    
                    Text("and")
                    Button {
                        
                    } label: {
                        Text("Underlined 2")
                            .underline()
                    }
                    
                    Text("Post prefix text")
                }

If you could suggest any possible workarounds, that'd be very helpful. Alternatively, if you could point me to the relevant part of the codebase, I'd be more than happy to look into a fix.

Looking forward to your response.

@MussaCharles
Copy link
Author

I have added code sample for the attached screenshots above.
Mind having a look? @muukii

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

No branches or pull requests

1 participant