Clarification of WebKit version numbering?
In my app, I am currently working around a problem in the released WebKit (418) where [WebView setSelectedDOMRange: affinity:] ends up selecting things outside of the range. This problem appears to be fixed in TOT, which has a version of 420+. I would like to put a test in my code now so that I can bypass my workaround when this newer WebKit becomes the release one, but am unsure as to whether the '+' in 420+ implies that TOT is working towards a 420 release or a 421 (or beyond) release. Or to put it another way, should my test be: if (version >= 420) or if (version >= 421) I realise that the bug fix could regress between now and a release which includes it. Matt Gough
Hi Matt, in the source of http://webkit.opendarwin.org/quality/reporting.html you will find a script for finding webkit versions. The + is added specifically for the nightly version of WebKit. We cannot, however tell you when a specific fix will make it into mainstream WebKit, as this is an internal Apple decision the WebKit team has no vote in. The Apple people will not tell you either, because they aren't allowed to. So for now, i would go with just looking for 420+, and testing in the next release if it's fixed. Don't make the mistake of just looking for the +, as older nightlies (like 412+) might not have the right fix in it. Kind regards, and good luck, Joost de Valk Matt Gough schreef:
In my app, I am currently working around a problem in the released WebKit (418) where [WebView setSelectedDOMRange: affinity:] ends up selecting things outside of the range. This problem appears to be fixed in TOT, which has a version of 420+.
I would like to put a test in my code now so that I can bypass my workaround when this newer WebKit becomes the release one, but am unsure as to whether the '+' in 420+ implies that TOT is working towards a 420 release or a 421 (or beyond) release.
Or to put it another way, should my test be:
if (version >= 420)
or
if (version >= 421)
I realise that the bug fix could regress between now and a release which includes it.
Matt Gough _______________________________________________ webkit-dev mailing list webkit-dev@opendarwin.org http://www.opendarwin.org/mailman/listinfo/webkit-dev
The + means that the version was built from the latest sources (as opposed to being an official release), and that it is newer than the version without the +. So 420+ is a version built from the latest sources that's newer than 420. As you say, it's working towards a 421 (or beyond) release. John On Apr 18, 2006, at 3:43 AM, Matt Gough wrote:
In my app, I am currently working around a problem in the released WebKit (418) where [WebView setSelectedDOMRange: affinity:] ends up selecting things outside of the range. This problem appears to be fixed in TOT, which has a version of 420+.
I would like to put a test in my code now so that I can bypass my workaround when this newer WebKit becomes the release one, but am unsure as to whether the '+' in 420+ implies that TOT is working towards a 420 release or a 421 (or beyond) release.
Or to put it another way, should my test be:
if (version >= 420)
or
if (version >= 421)
I realise that the bug fix could regress between now and a release which includes it.
Matt Gough _______________________________________________ webkit-dev mailing list webkit-dev@opendarwin.org http://www.opendarwin.org/mailman/listinfo/webkit-dev
On 18 Apr 2006, at 14:19, John Sullivan wrote:
The + means that the version was built from the latest sources (as opposed to being an official release), and that it is newer than the version without the +. So 420+ is a version built from the latest sources that's newer than 420. As you say, it's working towards a 421 (or beyond) release.
OK. So the only real pitfall I can see to me testing the version number to see if my workaround is redundant is that Apple could release one or more minor updates to WebKit that actually have higher version numbers than 420 (since 418 is the current release) and which don't include the fix, or is that not likely (i.e they would end up as 418.1, 418.2 etc). I realize you can't talk about future versions etc, but any further insight would be appreciated. Matt
I think it's safe to say that the major build number for a release would only go past 420 if the release included everything in 420+. John On Apr 18, 2006, at 8:00 AM, Matt Gough wrote:
On 18 Apr 2006, at 14:19, John Sullivan wrote:
The + means that the version was built from the latest sources (as opposed to being an official release), and that it is newer than the version without the +. So 420+ is a version built from the latest sources that's newer than 420. As you say, it's working towards a 421 (or beyond) release.
OK. So the only real pitfall I can see to me testing the version number to see if my workaround is redundant is that Apple could release one or more minor updates to WebKit that actually have higher version numbers than 420 (since 418 is the current release) and which don't include the fix, or is that not likely (i.e they would end up as 418.1, 418.2 etc).
I realize you can't talk about future versions etc, but any further insight would be appreciated.
Matt
participants (3)
-
John Sullivan
-
Joost de Valk
-
Matt Gough