Correctly match Safari version

[le717]

@gabceb For #35. As I said in my last comment, the information required was already present, just not used. However, the fixes retains the desired action for all other browsers, thus not resulting in breaking changes as I first thought.

This is is best reviewed by using the https://github.com/gabceb/jquery-browser-plugin/pull/37/files?w=1 URL to strip white space changes. It seems 1d235da did not fully fix #26, though I thought for sure it did...

[gabceb]

We are still not matching the Safari version correctly. I've pushed your commits and some changes to get testing running. Safari with user agent Mozilla/5.0 (iPad; CPU OS 7_0 like Mac OS X) AppleWebKit/537.51.1 (KHTML, like Gecko) Version/7.0 Mobile/11A465 Safari/9537.53 should return 637.51.1 but we are matching 9537.53 instead.

I'll add how to get testing work on #36

[gabceb]

Your commits are pushed at https://github.com/gabceb/jquery-browser-plugin/tree/le717-safari-version

[le717]

Do I need to close this and base further changes on that branch and you can merge that branch instead?

[lehni]

I just tested this, works like a charm, thanks! When will this be merged in? Time for a new release, perhaps? : )

[le717]

@lehni Looks like there is another issue @gabceb wants me to look at before a new release is pushed. Until then, you might want to pull in that file and leave a TODO to check back for a proper release soon.

[gabceb]

Feel free to leave this here and pull down the branch I created. Once that branch is merged with master this PR will close

[le717]

@gabceb Well this is interesting.
Some of the changes you (and/or I, don't recall which one) made to partially fix this only made it's way into the test/src copy and not the main dist copy, meaning #43 will create a conflict between the two versions. It might be best to get those changes resolved then get #43 merged, as it might be easier to sort out what was changed.

[le717]

Oh hey, I just got this working correctly, with all tests passing. I'll submit a PR and get the conflict sorted out at the same time. :)

[le717]

Closing in favor of #44.