Named internal links not understood outside reveal.js

[lechten]

Internal links work fine with reveal.js as documented.
However, the documention suggest to link with #/some-slide to a section with id #some-slide, which essentially results in broken links. (No fragment with the id /some-slide exists.)

Based on a quick test it seems to me that such links also work if I omit the slash. What is the rationale for including it?

[lechten]

To phrase this differently: Is there any reason why I should not use valid links when linking into reveal.js presentations?

My use case is as follows: I've got lots of internal links between different presentations and into presentations, and I'd like those links to be understandable by crawlers and search engines. Towards that end, the slash must not be used. Any suggestions or recommendations? In particular, readURL() removes # and / before looking up DOM elements, which ensure that links without slashes currently work. Are there any plans to change that behavior in the future so that links without slashes might not work any longer?

[lechten]

To continue my use case: If I just use valid links without leading slash when linking into presentations, the browser history does not work. PR #2282 fixes this.

[lechten]

In PR #2282, there is a problem with fragments that do not start with #/: In Firefox, on most slides with named ID links, the contents (including the progress bar) jump upwards before being displayed at their correct position, which is very distracting. Any ideas why this might happen? (This does not happen with Chromium.)

As an example, try moving back and forth between slides 3 and 4 of this presentation in Firefox.

[Dec. 6: Updated link to sample presentation.]