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

Search Support

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.

Learn More
Open

IOS 26 iPad with Magic Keyboard & Firefox Focus

jbr replied
jguthrie

I had have an iPad Pro running the latest IOS 26 and Firefox Focus. When I fire it up, if I have my keyboard attached, the cursor appears briefly for a second and then disappears. It’s like the cursor focus leaves the URL area of the browser.

If I disconnect my keyboard, I can click in there and use the on screen keyboard. Once I do that and enter anything [and hit enter], then it will work from that point. So this appears to only affect initial use of the app. I can click up there and type anything after that first submission and it works.

I had have an iPad Pro running the latest IOS 26 and Firefox Focus. When I fire it up, if I have my keyboard attached, the cursor appears briefly for a second and then disappears. It’s like the cursor focus leaves the URL area of the browser. If I disconnect my keyboard, I can click in there and use the on screen keyboard. Once I do that and enter anything [and hit enter], then it will work from that point. So this appears to only affect initial use of the app. I can click up there and type anything after that first submission and it works.

All Replies (5)

It sounds similar to earlier reports:

The last comment on that github issue indicates Firefox Focus is done being developed? Is that true? If so, shouldn’t it be pulled from the app store if it isn’t getting fixes or at least rebuild and have a warning on open saying the software is EOL?

End–of–life would mean no support and preferably pulling from stores. That's not the case. It's getting security fixes and OS–level compatibility updates necessary to build and ship. But it's not getting new features on iOS at this point. Hence why the bug was open to contributors who want to get involved with the project, and the HW keyboard compatibility matters to them.

Is there an official policy documented somewhere like what Cisco does? I’m not saying Cisco is perfect but uniform transparency would be good here.

Example Cisco EOL-policy. https://www.cisco.com/c/en/us/products/eos-eol-policy.html

No, there are no comparable product lines that would have support expectancy since sold etc. — most products are only limited by the underlying OS support (which is documented in their help pages) or HW architecture.

Specifically for Firefox, the versions supported are the ones being shipped, e.g. whattrainisitnow.com (so you get 115esr, 140esr, 151+ today, with certain parts of the year where the enterprise versions overlap, so you'd get extra 128esr for a bit or the upcoming 153esr when the time comes; train calendar on that link above as well…)

Focus on Android follows Firefox schedule being Gecko–based.

Focus on iOS however is powered by the system WebKit, so it gets its most key underlying platform updates via system iOS updates from Apple — and its capabilities are also mostly mapped to what the platform provides at its given iOS version.

There are still builds running using a matrix of systems, their health checked, tests being watched, certificates maintained and any necessary security updates released — if that were to change there would be an announcement in advance. (Basically as long as current Apple toolchain would allow building it without rewriting into Swift 6.x, it can still ship when needed.)

Béèrè ìbéèrè

You must log in to your account to reply to posts. Please start a new question, if you do not have an account yet.