Bug reported in v4.2:
---------------------
An image of a strange error message was sent to us by a user and after some investigation we found the perpetrator!
This error is triggered after 999 Memory Watch updates occur, because we had recently added logic that would reset Memory Watch to zero whenever it reached 999 to recover memory from useless data, but we placed the condition at the start of the relevant function instead of at the end!
So this bug will trigger if you’re on the Internet for a few hours and the 1,000th Memory Watch update is about to be made.
Let’s just call this the "999 bug" which has already been corrected... but we just gotta get the fix out to you! In the meantime you can disable "Browser Error Reporting" if you don't want to be disturbed by it.
The Classic Browser v4.2 is now available for download
------------------------------------------------------
1. The flexibility of the browser's address field has been extended once again! You can now type URLs, domains, IPs, or search text. The latter will now load your preferred search engine in a new tab with the search text passed to it.
The logic used to predict what the user is trying to do is very simple:
example 1: "x://hello.there" <-- it has a "://" so it must be a URL so just load it.
example 2: "hello.there" <-- it has a period so it must be a domain so add a "http://" to it and load it.
example 3: "hello there" <-- it has no period and no "://" so it must be search text which we pass onto the selected search engine.
2. You'll now find a new little surprise under... Main Menu > Browser Functions > Windows Help (<--Some of you need this)
3. You can now toggle the “sandboxing” (attribute) of a Tab from the Macro Menu under "Handy Tools". This feature is useful as an example, for when a website prevents you from copying things from it. We accomplish this by reloading the page with no JavaScript permitted thus disabling their ability to prevent you.
4. Corrected a bug with bad page titles containing HTML tags. Shocking stupidity by some website authors!
5. Due to the Classic’s exceptional page-loading speeds, we have removed the “Page Loading Cut-Off” option and replaced it with the new “Web Storage Reporting” tool.
Subsequently, we improved and streamlined the reporting of (1) Script Errors (2) PostMessages (3) Web Storage activity and (4) Request Headers, all of which should be of interest to developers.
6. ETag blocking gets a facelift and now also reports which of the ETags intercepted are the dodgy ones! NB: Etags have no effect on cacheless browsers but it's fun playing with them.
7. Numerous improvements/optimizations are also included.
