On: Things you (probably) don't know about Go

[papsosouid]

Things I still don't know because the site is just a solid black page with nothing on it.

[morsch → papsosouid]

I got the title slide and was stuck. Took me a while to find out that the space bar skips to the next page. Then I found the invisible 100px wide buttons left and right of the slide area.

Very annoying but I guess it looks better as a presentation. At least the mouse wheel should work, that was my instinctive reaction to skip forward and you could add that without affecting the visuals.

[ericson578 → morsch]

I'm on chrome on a mac, the pagedown/up buttons worked.

[enneff → papsosouid]

It's an HTML5 presentation. I apologize if it doesn't work in your browser of choice. Try viewing it in Chrome, instead.

[georgemcbay → enneff]

I viewed it in Chrome on Linux and it took me quite a while to figure out that you advance by clicking the solid black bars on the side of the slides (which don't even show if your browser window is too narrow). More of a UX issue than a technical one, I guess.

[cocoflunchy → georgemcbay]

Same here. Arrow buttons of some sort would help.

[jamesmiller5 → georgemcbay]

I hadn't even noticed how I was going through the presentation until you mentioned it.

[luchs → enneff]

The problem in Opera is your feature test in slide-deck.js line 762. At the time this part of the code executes, the DOM is not ready yet, so document.body is just null and the whole thing fails.

It does however work perfectly after executing window.slidedeck = new SlideDeck(); manually.

[tetha → enneff]

I used chrome and almost just exited the page until I accidentially clicked on the black part next to the slide. That's not a browser issue.

[nodrama → papsosouid]

Well, if you could see the first slide you could use the arrows to navigate.

[cocoflunchy → nodrama]

But you'd have to guess that. It's not standard behavior.

[nodrama → cocoflunchy]

You are right. I just wanted to let people know how to use it (I closed the site and reopened it because I didn't know either).

[4ad → papsosouid]

You probably need an HTML5 compliant browser.

[tedunangst → 4ad]

You also need to make sure your screen is wide enough. Running your browser on half of a 1920px screen isn't a supported configuration either.

[papsosouid → 4ad]

I have one. Perhaps the site needs HTML5 compliant markup?

[enneff → papsosouid]

It would help if you told me which one.

[jfoutz → enneff]

Chrome, OSX, Version 19.0.1084.56 fails

edit Version 22.0.1183.0 canary works, as does Firefox 13.0.1