-
Notifications
You must be signed in to change notification settings - Fork 80
Change way browser and version found #844
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Change way browser and version found #844
Conversation
objfullVersion = ''+parseFloat(navigator.appVersion); | ||
objBrMajorVersion = parseInt(navigator.appVersion,10); | ||
} | ||
// from http://stackoverflow.com/questions/5916900/how-can-you-detect-the-version-of-a-browser |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can you use the permanent link instead? http://stackoverflow.com/q/5916900/379593
This looks good except, there's not a good way to test this code, it has the "same" validity as the other chunk of code taken from a blog post found on the inter-tubes and that the code is not really maintainable. IMHO, should be ready to merge as soon as the comments I made are addressed but then again ... how can we make sure this new snippet is not introducing any problems that the previous block was accounting for? I would probably advocate for finding the bug in the previous block of code and correct it there. |
The issue is that there is no perfect way and more when browsers change the way they report their version, which made the previous one obsolete. I think this is fine as long as we test in all valid browsers. |
Ok, sounds good. We should check Safari, Chrome, Opera, Internet On (Feb-10-15|14:13), Antonio Gonzalez wrote:
|
Up to you. I normally check Safari, Chrome, and Firefox.
|
@ElDeveloper, that is a fantastic screenshot |
Are you testing on this branch or on the main site?
|
Apologies -- actually, this is for the main site as it currently exists, not the proposed changes, thereby merely corroborating the finding in the opening message. |
So apparently flake8 updated and is throwing all sorts of fun errors. I'll fix that in aseperate emergency pull request. |
I'm on it, see #846 |
almost done also ... |
Oops, pull request already in. |
Pull from upstream master. |
…refox-validation
ready for review again. |
👍 @ElDeveloper ? |
It still doesn't work in IE 8 i. e. no message about the website not working is shown. 😕 |
good to review again |
It now shows the appropriate message for IE8, however it shows the On (Feb-12-15|15:50), Joshua Shorenstein wrote:
|
Bluh, The issue is that the older browsers flat out won't run the version check javascript, so I defaulted it to just throw the error by default. Not sure whats going on with IE 10, but we don't support Opera so it's getting the default error page. |
So then the only open issue is IE 10. And we may also need to rephrase On (Feb-12-15|16:10), Joshua Shorenstein wrote:
|
Yup. IE isn't firing off the document.ready so I'll dig into that. |
Went old school and used |
If we don't support Opera should that be changed then? On (Feb-12-15|16:32), Joshua Shorenstein wrote:
|
I think we can have in the documentation that we support X browsers above Y version, and while the site is accessible with other browsers , we make no claims to usability. |
Agree, could you add that list to the help wiki?
|
@ElDeveloper could you check again that it works on the expected browsers? Seems like you have everything in your system to do this ... thanks! |
Added to the FAQ section. |
Thanks, looks fine:
https://github.com/biocore/qiita/wiki/Frequently-Asked-Questions
|
}); | ||
</script> | ||
} | ||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Extra whitespace.
Just tested this in all the browsers I have access to and it works just On (Feb-13-15| 5:50), Antonio Gonzalez wrote:
|
whitespace removed, merge ready. |
Change way browser and version found
There was a problem with firefox and opera where the version found was not the actual version of the browser. This new code fixes that.