Navigating specification HTML

[Richard Lewis]

Dear MO group,

The new(ish) specifications look very nice. But one thing I find a little difficult is actually navigating around the HTML document <http://musicontology.com/specification/>. When I follow one of the links in the table of contents to view information about a class or property, there's a JavaScript effect that scrolls the document to the <section>. However, this doesn't actually change the current window.location. Consequently, if I want to navigate back to the table of contents I can't use my browser's back function. And this is true of *all* the internal links, not just the table of contents links. So if I've followed a link to a property from a class, I can't use the back function to go back to the class. I wonder if the JavaScript scrolling thing can be modified to result in a new history point (i.e. a URL visit)? I notice that the <a> links do point to the <section>'s by id, so I think it might just be a case of altering the onClick handler defined from lines 144-157 of mo.js to modify the window.location property.

Richard

[Yves Raimond]

On Fri, Jun 20, 2014 at 5:29 PM, Richard Lewis <richar...@gold.ac.uk> wrote:

Dear MO group,

The new(ish) specifications look very nice. But one thing I find a little difficult is actually navigating around the HTML document <http://musicontology.com/specification/>. When I follow one of the links in the table of contents to view information about a class or property, there's a JavaScript effect that scrolls the document to the <section>. However, this doesn't actually change the current window.location. Consequently, if I want to navigate back to the table of contents I can't use my browser's back function. And this is true of *all* the internal links, not just the table of contents links. So if I've followed a link to a property from a class, I can't use the back function to go back to the class. I wonder if the JavaScript scrolling thing can be modified to result in a new history point (i.e. a URL visit)? I notice that the <a> links do point to the <section>'s by id, so I think it might just be a case of altering the onClick handler defined from lines 144-157 of mo.js to modify the window.location property.

Ah very good point Richard - I literally just noticed that today too! Can you raise a ticket on Github? I'll try to fix it asap

Best

y

Richard

--
You received this message because you are subscribed to the Google Groups "Music Ontology Specification Group" group.
To unsubscribe from this group and stop receiving emails from it, send an email to music-ontology-specific...@googlegroups.com.
To post to this group, send email to music-ontology-sp...@googlegroups.com.
Visit this group at http://groups.google.com/group/music-ontology-specification-group.
For more options, visit https://groups.google.com/d/optout.

[Richard Lewis]

On Friday, 20 June 2014 17:30:53 UTC+1, yves.r...@gmail.com wrote:

On Fri, Jun 20, 2014 at 5:29 PM, Richard Lewis <richar...@gold.ac.uk> wrote:

Dear MO group,

The new(ish) specifications look very nice. But one thing I find a little difficult is actually navigating around the HTML document <http://musicontology.com/specification/>. When I follow one of the links in the table of contents to view information about a class or property, there's a JavaScript effect that scrolls the document to the <section>. However, this doesn't actually change the current window.location. Consequently, if I want to navigate back to the table of contents I can't use my browser's back function. And this is true of *all* the internal links, not just the table of contents links. So if I've followed a link to a property from a class, I can't use the back function to go back to the class. I wonder if the JavaScript scrolling thing can be modified to result in a new history point (i.e. a URL visit)? I notice that the <a> links do point to the <section>'s by id, so I think it might just be a case of altering the onClick handler defined from lines 144-157 of mo.js to modify the window.location property.

Ah very good point Richard - I literally just noticed that today too! Can you raise a ticket on Github? I'll try to fix it asap

Here you go: https://github.com/motools/musicontology.com/issues/3

Richard

[Yves Raimond]

Perfect - thanks :)