Blank dark gray screen #2

Closed
christiangenco opened this Issue May 15, 2012 · 10 comments

Comments

Projects
None yet
3 participants

On Mac OS X 10.7.3 on both Google Chrome 18.0.1025.168 and Safari 5.1.3, the result of running git-playback[master*]% ./git-playback README.md generates playback.html as a blank dark gray screen.

From the Chrome developer Resources tab, the page appears to have successfully loaded highlight.min.js, jquery.min.js, and monokai.min.css. There are no errors in the javascript console.

This error occurs with every file I have tried to generate a playback.html for.

snaewe commented May 16, 2012

"me too" on Windows XP, Google Chrome 18.0.1025.168.

@mmozuras mmozuras closed this in ae1d605 May 19, 2012

Owner

mmozuras commented May 19, 2012

Even if files didn't exist or were empty, empty divs were still created. In this case, README was not written until 10th commit.
Thanks for pointing this out!

Issue still exists. Here's README.md's playback.html (looks like no lis were generated).

Owner

mmozuras commented May 23, 2012

Heh, I managed to break it again. Fixed it (again). Time to think about a better way to test bash scripts than just "I'll just run it for this one case".

TDD ftw. Trying again...

Owner

mmozuras commented May 23, 2012

Yeah, I guess I should use the same good engineering practices for bash scripts that I use for everything else ;) It's just doesn't come as natural to me yet.

I still need to get into the habit.

Now I see a static screen with README's first commit (sauce). All resources loaded correctly and there are no errors in the js console.

Owner

mmozuras commented May 23, 2012

Yup, that is correct. At the moment, there is no autoplay or visual buttons. Use left and right arrows to navigate.

...OH! Wow, this makes a lot more sense. Can I update your README with an example and a sentence that says "visually navigate through your commits with the arrow keys" or something?

Owner

mmozuras commented May 23, 2012

Thanks, will do! :-)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment