.slide h1 {
text-transform: capitalize;
}

is an anti-feature. It seems to cause Safari to capitalize a letter following a single quote (can’T) and the capitalization is not always wanted.

$.02

You could get rid of that behavior by removing text-transform: capitalize; from pretty.css in the rule for .slide h1.

regards

Thanks, Daniel

I don’t think you should be afraid of diverging from OSF where it can be improved.

• I have written a German tutorial for creating new S5-CSS-themes (raw styled, will be published with the known German S5-translation by Eric Eggert, soon). If anyone is able to do a better English translation than I could, you’re welcome!
• I am with brian (comment #53), and onclick=”go()� would be the better solution than javascript:go() where accessability is concerned!
• Great, Steffen (comment #54) did exactly the thing I was recently missing!

I think this could get a mess when trying to highlight some portion of text during a presentation.

So I’ve extended the JavaScript to be able to handle text-selections (i.e. movements of the mouse while holding the button).

First, I’ve added the following code at the bottom of slides.js:

var start_posX = 0;
var start_posY = 0;

function start_clicker(e){
  if (window.event) {
		e = window.event;
	}

  start_posX = e.screenX;
  start_posY = e.screenY;
}

function mouse_moved(e){
  return Math.abs(e.screenX - start_posX) > 10 || Math.abs(e.screenY - start_posY) > 10;
}

Then I’ve registered it with startup():

document.onmouseup = clicker;
document.onmousedown = start_clicker;

Note that these two lines are supposed to replace document.onclick = clicker;!

Then clicker() had to be adopted. Replace if (target.href != null || isParentOrSelf(target, 'controls')) return true; with if (target.href != null || mouse_moved(e) || isParentOrSelf(target, 'controls')) return true;

Now a slide won’t react (move to the next slide) if the mouse was moved more than 10 pixels either horizontally or vertically while holding down a mouse-button.

I’ve tested with Firefox and it seems to work.

- You use innerHTML, i’m not sure that’s as good a system as document.createElement, with createElement you cannot create invalid code.

- The next/prev links use javascript:go(), if you used the onclick=”go()” then you could used the DOM function setAttribute() to add IDs to the DIVs for anchor links, and dynamically update the hrefs to href=”#id” that way when you toggled the slide presentations it would jump down to the same slide text in both formats.

- in low resolution monitors, there is no scrolling of the text in FireFox and strange scrolling in IE 6.0, on windows. So i miss the last few bullet points.