Skip to content

Fixes #6693: fixes search functionality on iOS devices #6743

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

Conversation

ramizackaryshamir
Copy link
Contributor

@ramizackaryshamir ramizackaryshamir commented Apr 9, 2024

Fixes search functionality on iOS devices

Fixes #6693


Current: Behavior of search functionality on iPhone 12 Pro

current-behavior_iPhone12pro.mp4

Fixes #6693: Behavior of search functionality on iPhone 12 Pro

behavior-with-fix_iPhone12pro.mp4

…iate from isOpen props in Search component

change setIsOpen to setIsMenuOpen in TopNav component
organize hook initializations in TopNav component: useState, useRef, useRouter
Copy link

vercel bot commented Apr 9, 2024

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name Status Preview Updated (UTC)
react-dev ✅ Ready (Inspect) Visit Preview Apr 9, 2024 7:35pm

@facebook-github-bot
Copy link
Collaborator

Hi @MeetYourCreator!

Thank you for your pull request and welcome to our community.

Action Required

In order to merge any pull request (code, docs, etc.), we require contributors to sign our Contributor License Agreement, and we don't seem to have one on file for you.

Process

In order for us to review and merge your suggested changes, please sign at https://code.facebook.com/cla. If you are contributing on behalf of someone else (eg your employer), the individual CLA may not be sufficient and your employer may need to sign the corporate CLA.

Once the CLA is signed, our tooling will perform checks and validations. Afterwards, the pull request will be tagged with CLA signed. The tagging process may take up to 1 hour after signing. Please give it that time before contacting us about it.

If you have received this in error or have any questions, please contact us at [email protected]. Thanks!

Copy link

github-actions bot commented Apr 9, 2024

Size changes

📦 Next.js Bundle Analysis for react-dev

This analysis was generated by the Next.js Bundle Analysis action. 🤖

Five Pages Changed Size

The following pages changed size from the code in this PR compared to its base branch:

Page Size (compressed) First Load
/404 79.73 KB (🟢 -16 B) 183.63 KB
/500 79.73 KB (🟢 -16 B) 183.62 KB
/[[...markdownPath]] 81.51 KB (🟢 -16 B) 185.41 KB
/errors 79.91 KB (🟢 -16 B) 183.81 KB
/errors/[errorCode] 79.88 KB (🟢 -16 B) 183.78 KB
Details

Only the gzipped size is provided here based on an expert tip.

First Load is the size of the global bundle plus the bundle for the individual page. If a user were to show up to your website and land on a given page, the first load size represents the amount of javascript that user would need to download. If next/link is used, subsequent page loads would only need to download that page's bundle (the number in the "Size" column), since the global bundle has already been downloaded.

Any third party scripts you have added directly to your app using the <script> tag are not accounted for in this analysis

Next to the size is how much the size has increased or decreased compared with the base branch of this PR. If this percentage has increased by 10% or more, there will be a red status indicator applied, indicating that special attention should be given to this.

@@ -110,7 +110,6 @@ export function Search({
createPortal(
<DocSearchModal
{...options}
initialScrollY={window.scrollY}
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Awesome stuff.

is this the actual fix? Can you explain what the problem was and how this fixes it?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hi @rickhanlonii 👋

Thanks so much! Yep, line 113 is the actual fix. I didn't take a look into the internals of the library, but it looks like the bug might actually be in the Autocomplete library. It looks like their DocSearchModal component has a bug in the modal design, which is causing the screen to freeze once the device width is less than about 755px.

width_at_755px_vs_741px.mp4

Copy link
Member

@rickhanlonii rickhanlonii left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM - I tested on desktop and mobile to confirm nothing broke, and the fix works.

If you can sign the CLA I'll merge!

@ramizackaryshamir
Copy link
Contributor Author

Thanks so much, @rickhanlonii 😀

@rickhanlonii rickhanlonii merged commit 11a7479 into reactjs:main Apr 10, 2024
4 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

[Bug]: Search functionality not working correctly on react.dev in Safari on iOS real device (iPhone 12 Pro)
3 participants