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

ค้นหาฝ่ายสนับสนุน

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

เรียนรู้เพิ่มเติม

FF does not let me enter new url or search terms!

  • 3 การตอบกลับ
  • 3 คนมีปัญหานี้
  • 66 ครั้งที่ดู
  • ตอบกลับล่าสุดโดย michael1508
  • แก้ไขปัญหาแล้ว

Using iOS 9.1 on IPad AIr 2.

No problem with new installed Firefox. But after building up history of visited websites, FF does not accept new entries in the address/search field. It always auto-completes my entry with existing URLs out of my visit history after the first 2 entered letters.

What am I doing wrong?

Thx, Michael

Using iOS 9.1 on IPad AIr 2. No problem with new installed Firefox. But after building up history of visited websites, FF does not accept new entries in the address/search field. It always auto-completes my entry with existing URLs out of my visit history after the first 2 entered letters. What am I doing wrong? Thx, Michael

วิธีแก้ปัญหาที่เลือก

Found the problem: it only appears, if I use the Swype addon keyboard, which I installed. It works fine with the standard keyboard.

Still annoying, but at least I know how to avoid.

Cheers, Michael

อ่านคำตอบนี้ในบริบท 👍 1

การตอบกลับทั้งหมด (3)

Dear Michael, There are few things that you must fix, because i don't have a lot of information about your problem.

1) Go to settings >> General >> Keyboard >> Then disable Auto-Correction & Check Spelling

2) When that show up click on X botton and disable it That's result of writing fast.

Hope you solwed the problem :D

วิธีแก้ปัญหาที่เลือก

Found the problem: it only appears, if I use the Swype addon keyboard, which I installed. It works fine with the standard keyboard.

Still annoying, but at least I know how to avoid.

Cheers, Michael

Still same Problem with Swype and Firefox. Also tried SwiftKey. Works fine with every app, but also not with Firefox!

Seems to be a FF issue....