Quote from: turner3d on June 18, 2014, 05:28:50 PM

Quote from: fullhdpixel on June 18, 2014, 04:50:58 PM

Quote from: turner3d on June 18, 2014, 04:32:17 PM

The website updates have potential, but they're all kinds of jacked up. It's great that the design attempts to be responsive, but there are many issues.

Chrome:
No links on the page work when the browser is wider than 895px
At some resolutions, the mobile drop-down-menu link and the standard header menu are there at the same time

Firefox & IE:
At anything over 895px, the video occupies the entire screen making nothing else visible - no links, nothing

All:
The ajax functions in index.js (updateBittrex, updateCoinnext, updateAGX) are all hitting scripts which are throwing "403 Forbidden" errors

Is there no dev server for the site where updates can be tested before launched? IMHO, the site is doing nothing but hurting credibility in its current state.

Hi,

Let me go through each one of these.

"No links on the page work when the browser is wider than 895px".
This is simply false, I've tested this in chrome and it works fine.
Links are working across the board work now that the video background is disabled

"At some resolutions, the mobile drop-down-menu link and the standard header menu are there at the same time"
There's an overlap of 20px, which doesn't make that much of a difference. It's for users that want both at the same time.
Sure it is... "It's not a bug, it's a feature!" I'm just being picky on this one anyway... not really a big issue

"At anything over 895px, the video occupies the entire screen making nothing else visible - no links, nothing"
I was just testing this on the server, I'll move on to local development and resolve these issues first.
As mentioned above, I'm fairly certain that this was responsible for the links not working on the earlier issue - maybe a z-index problem with the video player?

"The ajax functions in index.js (updateBittrex, updateCoinnext, updateAGX) are all hitting scripts which are throwing "403 Forbidden" errors"
PHP is not enabled on the server. Not my fault.
If PHP is not enabled on the server, at least disable the ajax calls to the PHP scripts. Having stuff on a page that is broken is bad enough - having it there and knowing it's broken is worse. Also, what kind of lousy hosting provider doesn't have PHP enabled on the server? That's just crazy.

Responses to the responses above. Please note that I do understand and appreciate the work that has gone into this, and I am not in any way trying to be a troll. It's just that this page is the face of the entire currency; the importance of both its look and functionality are not to be taken lightly.

I am glad for what you found and do not believe in anyway you were doing so in a negative light. Your findings are crucial and in no way trollish.