Image with error attached below. FFox 107.0 (21907) When I press the "Home" button/icon in FFox for IOS to go to the startup page I am getting an error message "The URL can't be shown / WebKitErrorDomain". I believe this is an evolution of the error I reported here: [http://example.com https://support.mozilla.org/en-US/questions/1397009] However, it looks like there's been a FFox update in the last day (If I recall the version number correctly from the last one) and the error has changed. Reliably reproducing this: - Start FFOX - press a startup page icon to access a site OR enter a URL directly in the address line. Look at one or more pages. - press FFOX "Home" button/icon to get back to FFOX startup screen - error occurs - The URL line when the error occurs is ".enx%20la%20l". Info: I reported a '''very similar''' error here: [http://example.com https://support.mozilla.org/en-US/questions/1397009] about a week ago. A few days ago it cured itself. Then today it started again but with a slightly different URL and a completely different error message. However, the oddball URL tells me the two are closely related. Recap: - I've been using FFOX for years without issue on this phone. - Everything else including accessing web sites seems to be working normally. - There have been no related configuration changes on my part since the last error but it does look like FFox has updated. I don't know how to see the version number in the previous post so I'm not sure. - There have been no IOS updates on the phone in the last couple months (auto update is off) The TLD/url (.enx) does not appear to be a valid TLD. It's either something FFox is using internally or perhaps IOS is supplying it (seems unlikely but possible). I do have the usual array of sites on my startup page as icons. None of the sites iconed on the startup page has been changed recently. If I close the (al)l tabs and/or instead start a new one, I get the startup screen as expected. So there are apparently no network access issues. This is 100% reliable with no delays. This definitely looks like a BUG to me or an internal issue. Is there a better way to report a bug?