Mozilla plans to launch a brand new secure model of the Firefox net browser quickly. The new model, Firefox 67.zero.1, updates secure variations of the net browser.
The replace shouldn’t be accessible but however Firefox customers will get it as a part of the net browser’s computerized replace system or as a standalone obtain and set up.
Administrators can set up the standalone model over an present model to improve it with out shedding any of their information.
Mozilla released Firefox 67.0 on May 21, 2019. The new net browser launched WebRender assist to a fraction of the person base and included efficiency enhancements.
The Firefox 67.zero.1 launch notes will not be out but and there may be surprisingly little data accessible on the time as to what the replace fixes within the secure model.
A fast scan of Mozilla’s bug monitoring website [email protected] returned one concern that Mozilla mounted in Firefox 67.zero.1. The concern, filed below bug 1554029, means that Firefox’s downgrade detection failed for non-minor to minor variations improve.
Firefox would see the improve from Firefox 67.zero to 67.zero.1 as a downgrade and set off the downgrade warning immediate in that case to warn customers about potential conflicts which will come up out of this.
Mozilla added a compatibility examine to Firefox to stop information corruption points when directors downgrade Firefox to an older model. Downgrades could result in information corruption and cargo errors if the model Firefox is downgraded to makes use of totally different codecs or information varieties than newer Firefox variations.
All Firefox customers who would improve the browser from Firefox 67.zero to Firefox 67.zero.1 would learn by Mozilla on the primary launch after the improve that they have been about to launch an older model of Firefox and that that warning immediate prevented that from occurring.
The immediate wouldn’t look too good and would trigger a number of confusion amongst customers because it provided solely two choices: create new profile or stop. Firefox customers wouldn’t be capable to use the browser with the previous profile or use it in any respect as a consequence.
The concern is brought on by a math error when evaluating the previous model and construct IDs to the brand new variations as defined on the Bugzilla itemizing by Dave Townsend.
We construct compatibility variations as
_ / . the place the construct ID’s by default are a numeric illustration of the date that the construct occurred.
Previously we tried to mangle this into a sound toolkit model by changing to
. . if the construct IDs have been the anticipated size. We additionally break up every construct ID into two model components because the model comparator could not deal with their full dimension.
This mangling fails when evaluating a significant model with a brand new patch model:
. . will get in comparison with .1. . . Unless that patch model (1 right here) was larger than the construct ID (presently within the tens of tens of millions) the patch launch would look like older than the earlier model.
It is unclear if Firefox 67.zero.1 addresses different points. We will replace the article as soon as the official release notes are printed by Mozilla.