IBrowse Home   News   Store   Download   Known Issues   Add-ons   Search Engines   FAQ   Mailing Lists   Documentation
Development Radar: 612 issues open (30 assigned) and 1025 blown away
Did you know... you can rearrange browsers by drag'n'dropping the tabs?
Known IBrowse 2.5 Issues
New features Known issues Documentation Changes lists History log FAQ
updated 23 October 2019, 12:20:32 UTC
With 13 years between the release of IBrowse 2.4 and 2.5, I suppose it is to be expected that there have been a few teething issues. Where we can, we will resolve or issue solutions asap. For problems that require modifications, we are taking note of any issues reported and will release free updates to fix them.

If you are having trouble with IBrowse 2.5 which isn't explained below, please raise the issue with us, preferably via the mailing list where other users can offer advice as well as us, or directly at support@ibrowse-dev.net.

Crashes with HTTPS connections on 68020 and 68030
HTTPS slowness on 68k hardware
Localization, catalogs, .cd/.ct files
Store Problems
Installer Problems [fixed in 2.5.1]
Crashes after installing 68020fpu, 68040 or 68060 versions [fixed in 2.5.1]
Enforcer/MuForce/Cyberguard hits involved IBTextAreaField.ibcc [fixed in 2.5.1]
Context sensitive mouse pointers don't work [fixed in 2.5.1]
HTTPS proxy functionality broken [fixed in 2.5.1]
Not loading on AmigaOS 3.0 [fixed in 2.5.1]


Crashes with HTTPS connections on 68020 and 68030
Unfortunately, it has come to light that AmiSSL v4 currently requires an FPU, which is an optional additional chip on 68020 and 68030 cards (68040 and 68060 have a built-in FPU). If you don't have an FPU, then since AmiSSL v4 uses FPU instructions, this causes the crash. We can't do anything about this in IBrowse, but we will make sure the AmiSSL team fix this for AmiSSL 4.4.

HTTPS slowness on 68k hardware
It is possible that many of the new security ciphers available in AmiSSL v4 may pose trouble for real 68k processors, even for a 68060. You will have experienced similar with IBrowse 2.4 and AmiSSL v3, had you ever enabled DH on IBrowse's cipher settings page (we disabled it by default, due to performance issues). We are investigating reports of slowness of AmiSSL v4 in IBrowse 2.5, but we are currently suggesting playing with disabling various options in IBrowse's cipher settings to see if that yields an improvement. Likewise, perhaps disabling TLSv1.3 is worth a try too, to see if that helps. Once we have more information on this, we'll update this page.

Localization, catalogs, .cd/.ct files
We thought it only sensible to release IBrowse 2.5 as quickly as possible, without waiting for translations to be made. Most localized text in IBrowse 2.5 is the same as 2.4, so the 2.4 .catalog files supplied will continue to work fine in the most part. For the 20-30 or so new strings in 2.5, only english will be displayed. Starting with IBrowse 2.5.1, we now have updated full 2.5 translations for Danish, Spanish and Swedish. Translators for other languages are welcome to contact us, and we'll gladly send you the .cd/.ct file and give you details on the special mailing list we have set up to assist translators.

Store Problems
We hope most customers have been pleased with their experience of our new web store. We tried to make things as simple and straightforward as possible, especially where it comes to upgrades where our server can check for valid keys, etc, live online in real time, with only manual verification of keys and PayPal transactions required to minimize fraud. This streamlining hopefully has made the process for you all quick and painless. A few bugs did crop up in the early stages which we fixed immediately after we were made a where of them. These included a bug in the e-mail address validator reporting some addresses as invalid and broken upgrade payment links that were e-mailed out.

If you have either paid for a new license or put in an upgrade request, please check your spam/junk folder. New keys are e-mailed out - this has already been done for all new orders and there are none left pending for more than a few hours at the most. Likewise for upgrade requests, all pending requests have been approved, and you should have received an e-mail by now with further instructions. We have had a few isolated cases of e-mails bouncing, but we hope to have remedied this now and have resent failed e-mails. Should you require assistance with a store related issue, please don't hesitate to contact us at store@ibrowse-dev.net and we will do our best to help you.

Installer Problems [fixed in 2.5.1]
There have been reports of the install utility failing with errors. Unfortunately, some of the newer and third party Installer programs are incompatible with the official versions released for AmigaOS and some do not implement or parse the language properly. This program is usually found in SYS:Utilities. For AmigaOS 4.1FE, you will need to ensure you are using 53.8 or higher (53.9 was supplied with 4.1FE Update 1) due to bugs in earlier 53.x versions. For AmigaOS 3.x the official v43 Installer is a good starting point. Equally, the v44 and v45 Installer supplied with AmigaOS 3.5 and 3.9 respectively are fine. For MorphOS, we have had one report of issues although we are not sure which version of Installer was being used, but we do not it could properly not parse our valid - there could be issues with missing MUI: assigns, etc, and MUI classes being installed in a wrong location, depending on your MorphOS version and install. We will monitor reports from MorphOS users and apply fixes to the IBrowse install script where required.

Crashes after installing 68020fpu, 68040 or 68060 versions [fixed in 2.5.1]
If you downloaded IBrowse 2.5 within 4 hours of release, before 21:30 UTC on August 30th, there was an error in the archive where the executable bit on the spatch program was not set. This was quickly spotted and fixed - re-downloading the archive or protect +e "IBrowse2.5-020+/spatch" will get you going. What was happening was that the image decoders and javascript.library were not being installed at all. However, even though the installation was faulty, we plan to address the issue of the crashes even happening in such cases, instead of exiting gracefully with an error.

Enforcer/MuForce/Cyberguard hits involved IBTextAreaField.ibcc [fixed in 2.5.1]
A bug in the TextEditField class means that hits (should be harmless) can happen when loading webpages that have <textarea> elements or opening the display/edit source window, when using a version of MUI older than 5.0. This has been fixed for the next update.

Context sensitive mouse pointers don't work [fixed in 2.5.1]
IBrowse's own custom context sensitive mouse pointers are no longer being used at all, but should be if using MUI 3.x. This has been fixed for the next update. If using MUI 4.x or higher, context sensitive pointers will be working, using MUI's pointers.

HTTPS proxy functionality broken [fixed in 2.5.1]
We are currently investigating reports of the HTTPS proxy feature not working as it did in 2.4. It looks to be related to the new TLS SNI (Server Name Indication) feature that IBrowse 2.5 started using. This will be fixed in the next update.

Not loading on AmigaOS 3.0 [fixed in 2.5.1]
Unfortunately, this was an oversight on our part. Whilst optimising and improving the startup code in IBrowse, partly due to the OS4 port, we neglected to realise that Kickstart 3.0 only has keymap.library v37, whilst IBrowse 2.5 incorrectly asks for a minimum of v39 (the version number of most OS components in OS3.0). We apologise for this mistake and it will be fixed in the next update.

IBrowse is © 2001-2019 Stefan Burstrom, © 1995-2001 Omnipresence Intl. All rights reserved.
[counter]