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

Bug: Search functionality not working correctly on react.dev in Safari on iOS real device (iPhone 12 Pro) #4052

Closed
ramizackaryshamir opened this issue Mar 12, 2024 · 1 comment

Comments

@ramizackaryshamir
Copy link

Steps To Reproduce

  1. Open react.dev in Safari on iPhone (real device)
  2. Tap search icon: note that search function is working as intended
  3. Scroll down to "Write components with code and markup" section
  4. Tap search icon: note that action doesn't open search
  5. Scroll down again and tap the search icon several times: note that action doesn't open search
  6. Repeat step 5: note that eventually screen freezes

An issue has also been opened in the react repository

The current behavior

Search functionality does not work correctly on iOS real device (iPhone 12 Pro).

react_github-bug-report_current-behavior-1.mov

Since search functionality is currently working as expected on macOS, both in Chrome and Safari, the issue might be in implementation of Algolia InstantSearch iOS:

react_github-bug-report_current-behavior-2.mov

The iOS real device that this behavior was recorded on is using the current iOS version:

react_github-bug-report_ios-version


The expected behavior

Search functionality is working as expected on macOS, both in Chrome and Safari. Should work similarly on iOS real device:

macOs Chrome

search-functionality_chrome-macOS-v14.3.1.mp4

macOS Safari

search-functionality_safari-macOS-v14.3.1.mp4
@Simek
Copy link
Collaborator

Simek commented Mar 13, 2024

Hey @MeetYourCreator, this is repository contains the source code of reactnative.dev, not react.dev. Those website are separate entities and don not share any code.

Usually I would transfer the issue to the correct repo, or recommend re-creating it in the correct repository, but I have seen that you have already posted this issue in other places, so I'm just going to close this one..

@Simek Simek closed this as not planned Won't fix, can't repro, duplicate, stale Mar 13, 2024
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

2 participants