Windows 10 reached EOS (end of support) on October 14, 2025. If you are on Windows 10, see this article.

Avatar for Username

搜尋 Mozilla 技術支援網站

防止技術支援詐騙。我們絕對不會要求您撥打電話或發送簡訊，或是提供個人資訊。請用「回報濫用」功能回報可疑的行為。

了解更多
此討論串已被封存。 如果您有需要幫助，請新增一個新問題
封存

Cannot use Search/URL field with physical keyboard (iPadOS 26)

Firefox Focus 搜尋
wirkutskijkarl replied 1 年前
hymnals-chignon.0g
hymnals-chignon.0g

Please help me resolve the following problem: When using a physical keyboard attached to iPad, when I tap in the Search bar of Firefox Focus, I am unable to enter any text because the keyboard focus does not remain in the search bar. I have found the following workarounds: If the browser has a page already loaded, I need to tap the Delete icon in Firefox Focus in order to clear the page. Or, if I temporarily detach my physical keyboard, then I can use the Search bar as expected. After doing either of these things, the Search bar works properly. (Note: The problem described above seems to have started happening with iPadOS 26. It did not occur in iOS 18). Thank you for your assistance.

Please help me resolve the following problem: When using a physical keyboard attached to iPad, when I tap in the Search bar of Firefox Focus, I am unable to enter any text because the keyboard focus does not remain in the search bar. I have found the following workarounds: If the browser has a page already loaded, I need to tap the Delete icon in Firefox Focus in order to clear the page. Or, if I temporarily detach my physical keyboard, then I can use the Search bar as expected. After doing either of these things, the Search bar works properly. (Note: The problem described above seems to have started happening with iPadOS 26. It did not occur in iOS 18). Thank you for your assistance.

所有回覆 (1)

wirkutskijkarl
wirkutskijkarl

I’ve run into the same problem on iPadOS 26 with a physical keyboard. For me, detaching the keyboard and re-attaching it temporarily lets me type in the search bar, but it’s annoying to do every time. Hoping Mozilla will fix this in a future update because it never happened on iOS 18.